Workflows and Flush Agent

Hi @chanutejo 

I would recommend you to implement sling dynamic include so that particular component alone won't be cached as part of the page and always displays real time data.

https://experienceleague.adobe.com/en/docs/experience-manager-learn/foundation/development/set-up-sling-dynamic-include

Hi @chanutejo 

Ideally, You should not cache this component at the dispatcher level. To implement dynamic caching of a component, one of the solutions could be using Sling Dynamic Include.

However, if you want to go ahead with your solution, you can write a scheduler that can trigger the workflow and flush agent programmatically.

Regards,
Arpit Varshney

I would suggest you to consume the API data from the frontend side so that app is not cached and it will get fresh data on each request. That’s how normally we do. 
I believe file data are cached on dispatcher so you need to identify the pages on which the component is authored and you can setup a corn expression on dispatcher to execute the cache flush. This might not work if you are on AEMCaS. Sling dynamic include help but in case the request will still go to your aem server to get the api response but from front end you can avoid the backend call. Check below blog to how do a flush programmatically https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-call-flush-agent-programmatically-for-flushing-referenced/m-p/279850

@chanutejo , 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.