#Revalidate path not working as expected

2 messages · Page 1 of 1 (latest)

open fjord
#

I have an app that reads data from a headless CMS. I want to use a webhook in the cms to revalidate the pages that has been changed when you publish them in the cms, however running revalidatePath on them doesn't seem to work at all. I have the following route: /[[...slug]] for all pages, so I run revalidatePath with /[[...slug]] but it doesn't work.

I also tried using revalidateTag, but as we're not using fetch I can't tag anything. I tried using unstable_cache, but as the cached data is recursive it can't stringify it, so taht's not possible either.

All pages have export const dynamic = 'error' and export const dynamicParams = false, so I feel like this may be related to that.
Either I am missunderstanding how revalidation works, or there's a bug in nextjs. Is there someone who knows what the problem might be?

open novaBOT
#
Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

      🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in <id:customize>

      ✅ You can mark a message as the answer for your post with `Right click -> Apps -> Mark Solution`
      (if you don't see the option, try refreshing Discord with Ctrl + R)