HI @Eljon - we understand you were comfortable with Twist, but remember that the Twist system was also new to you once - so within no time, you should be comfortable using the Community!
We do want to step in - we've noticed you've opened multiple threads yourself, as well as commented on other peoples posts asking for us to look at your issues which are not necessarily related.
There are community guidelines we need to follow - and we need to be aware that all publishers in the community have been working with Ezoic for several months now. There shouldn't be a reliance on our agents to help like maybe you were used to right at the start.
Further, when questions are asked in the community, it shouldn't be expected that an Ezoic agent will immediately be able to respond to your issue in real-time. The community is largely for peer learning and troubleshooting, not for consistent direct support, and the expectations are that after several months with Ezoic publishers will be largely self-sufficient in using our tools.
On the question you've asked, I used the Chrome Extension to look into the issues on the page you reported in an earlier thread, and there were new vary headers from the origin that appeared to be preventing the page from being cached by Ezoic properly.
I'd highly suggest you use this guide to troubleshoot: https://support.ezoic.com/kb/article/how-can-i-use-leap-and-ezoics-chrome-extension-to-pass-core-web-vitals
Then, you can use this guide as well: https://support.ezoic.com/kb/article/is-ezoics-cdn-or-the-caching-app-working-on-my-site