So I'm pulling content from a CMS (directus). For some reason right now it's not pulling new content even if I rebuild on cloudflare... That's the biggest issue.
Regarding fetch request caching in next-on-pages, we store the response in the workers cache API (this is configurable) when nextjs asks us to, and retrieve data from the cache API when nextjs asks us to. Obviously there's more going on under the hood, but that's the very simple explanation
You can use revalidatePath / revalidateTag to trigger a revalidation for the fetch requests or all fetch requests under a route. That will be the on-demand revalidation section in the docs
You could add an API endpoint that you call that triggers the revalidation and is authenticated with a secret. Maybe a way to set it up to be automatically called on a successful deploy. Not sure.
My personal opinion would be to have your data fetched from the CMS and have the fetch request set to revalidate on an interval, then when the CMS makes a change, trigger a revalidate for that route. Ideally your CMS would let you do something like a webhook or http call on a publish to trigger an endpoint that can clear the relevant route.