Published Doc: Application Error (server-side exception)

[samlittlefair]

Hey Neil,

Thanks for describing your issue.

We talked about it on the support team, and all agreed that this looks to be most likely the Next.js 13 caching issue. We've never seen this sort of strange rebuild behavior anywhere else.

You could follow the main thread, and also upvote the linked GitHub issue:

Caching issue with Next.js App Router - Vercel Deployment

I am about to pass off the project to a client. Is there a reliable way to ensure their updates in Prismic get reflected on the frontend? I am getting wildly inconsistent results with the revalidateTag webhook. Should I also trigger a build on the Vercel side after the revalidate endpoint is called? Please help! and Thank you Edit: I would like to add my changes (in even in Production) are reflected in Draft/Preview mode but not on the live site (after publishing).

Sam