Unable to access Product Detail Page for newly added product

[cist-aiho]

Hi.

I am not able to access Product Detail Page for newly added product.

The system throws 404 error, I debugged the code it is coming from the OOTB method getProductForCode in DefaultProductService.

It always return empty list. (no product found with the code) even though the product is really exist both stage and online version with APPROVED status (checked in BO and flexiblesearch query in HAC)

The weird things is our PDP will be fine if we access it by tomorrow (we have to wait at least 24hours).

What happened actualy? is it cache issue?

These are solutions that I've been implemented but still failed :

1. add property flexblesearch.query.ttl.time and regioncache.querycacheregion.ttl, set its value to 0.

2. Before our Product Page controller call the OOTB method, I called clearCache() of CacheController class for each region

3. clear cache from HAC. Monitoring -> Cache -> Clear cache

Really appreciate if anybody can help me. Since I've been stuck for 3 days.

Thanks.

Note : The hybris version we are using is 6.6

[ruchi_tripathi]

Can you also please verify its not some SearchRestriction on product which is causing this?

Though it cannot be responsible for 24 hours delay.

[former_member704915]

Hello,

Just a random thought on your issue. Are you providing values for product onlineDate and offlineDate ?

If yes, then this seems to be a possible time zone issue. Suppose, you give the product online date as 21st Oct, 2020 and the database and app servers are hosted in US time zone (PST) , but you are located in Indian Time zone (IST). So, you won't see the product because there is a difference of roughly 12 hrs between PST and IST. So, you see the date as 21st Oct, but unfortunately the date at server level is still 20th Oct.

If you are not making use of product onlineDate and offlineDate, then please disregard the above explanation. The issue may be something else then.

Thank you!

[cist-aiho]

Hi, thanks for your answer.

We solved this issue a week ago.

You were right, it is due to the existance of onlineDate and offlineDate.

There is known bugs from SAP. For those who experience the same issue, please refer to this link.

https://apps.support.sap.com/sap/support/knowledge/en/2515118