Stale CMS content on frontend in prod, am I crazy to expect fresh data?

[phtmgt]

Posting this here, as they've intentionally made it too much trouble to post a bug (reproduction repo + steps, etc.)/

I spent the good portion of a few days to try to deploy Payload 3 + next.js 15 in standalone mode only to find out changes in content do not show on the frontend, unless the docker container is stopped and started. Is this expected behavior?

[16:19:40] INFO: Revalidating old page at path: /---
[16:22:40] INFO: Revalidating page at path: /---

This makes no difference. The changes only show after restart. Is there a way to run an optimized build with fresh content or do I have to run in dev mode?

[DanRibbens]

It sounds like your revalidation of changed content isn't working.

This is how we handle revalidation in the website template using collection hooks:

payload/templates/website/src/collections/Pages/hooks/revalidatePage.ts

Line 7 in 4defa33

export const revalidatePage: CollectionAfterChangeHook<Page> = ({

Did you start from the website template?

The reason we ask for reproductions is to remove ambiguity since we can't troubleshoot without code and steps to take to see the issue.

[phtmgt]

It sounds like your revalidation of changed content isn't working.

This is how we handle revalidation in the website template using collection hooks:

payload/templates/website/src/collections/Pages/hooks/revalidatePage.ts

Line 7 in 4defa33

export const revalidatePage: CollectionAfterChangeHook<Page> = ({

Did you start from the website template?

The reason we ask for reproductions is to remove ambiguity since we can't troubleshoot without code and steps to take to see the issue.

You are totally right. I found my answer here:

#8596

My revalidation was flawed, as I have created a new collection (as a copy of Pages) and forgot to check my revalidation flow.