Hello, happy holidays. We are running umbraco in our project to serve as a headless CMS. We are running into an issue, where when the umbraco part of our app is not used for a bit (~few hours), then the next load of any content is extremely slow. Our only idea thus far is to simulate traffic by hitting the umbraco endpoints to keep them warm, but we hate the idea... How is this situation usually solved? Thanks as always, MF.

Where are you running your project? It looks like your Umbraco application shuts down after some time. In Azure, make sure you enable 'always on' if you are using a web app. On IIS make sure you disable recycling the application pool after (30) minutes of in activity.

In Azure, the application has Always On turned on. Other parts of app/caches work normally even after long time of being unused. Except umbraco.

Hmm I can't say I recognize the behaviour. But we haven't run Umbraco 14+ yet, so maybe it's specific to newer versions. In the mean time, did you configure Umbraco correctly for Azure (it's a long stretch, but I'd thought I mention it): https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/azure-web-apps

Anything interesting in the logs? Eg. reboots etc.?

Hey, thanks for the responses. We will try to do the Azure config steps, i will notify about how it went.

Next documentation to check is this one: https://docs.umbraco.com/umbraco-cms/extending/filesystemproviders/azure-blob-storage

From this we were missing the image sharp cache step (which sounds like it will solve the problem), will implement and respond if it fixed the issue. (It will take ussome time again, because we're testing if it stops working after not using it for a while...)