Caching pages that contains components with errors

Hi @julio_baixauli Over here you are waiting for the response and then trying to serve the content. And meanwhile there is a request time out and you must have handled the execption and that's the reason for the response code as 200.

IMO, when you need to cache the http response from the cache, you should write a Scheduler via a Sling Job and store the data within the AEM. This way your content will be served faster during the first load and going forward as well and the load on the server will also be reduced.

Over here as you will be syncing the data from commerce to AEM author. So, once the data is there in the AEM author instance, verify it by handler/listener/workflow using any of the flag that would be set while storing the data and replicate it to the other publish instances as well.

This way it will be fully automated as well.

Hope this helps!

Thanks

Hi Julio,

Once you get an exception from commerce service, set response status to 500 for this request.

Then tell Dispatcher to not cache 500 and ask Dispatcher to do the logic you need Dispatcher to do.

Regards,

Peter

@julio_baixauli : Component errors specifically in sling model could be associated with your component dialog values. Therefore you should be seeing the same error on author instance as well and page should ideally not be replicated.
Once the error is corrected by authoring dialog field values, page can be published and that should clear the cache for your page on dispatcher and users would start to see updated page without error.
Please let me know if I have assumed something and this is not the case for your error.
thanks.

@julio_baixauli Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.