Serverless functions started timing out after `revalidateTag`
Unanswered
Plague posted this in #help-forum
PlagueOP
I'm caching a very small amount of data, just some categories I use to filter my content that's fetched from Contentful, I only just added this cache and when testing the revalidation using
None of these fetches take more than a second, let alone 10 and they are also memoized so only one fetch is every made, something weird is going on as
revalidateTag all my non-API routes so just the PPR functions when looking at the vercel build logs, are timing out nowNone of these fetches take more than a second, let alone 10 and they are also memoized so only one fetch is every made, something weird is going on as
revalidatePath didn't cause any issues, but for some reason revalidateTag did.4 Replies
PlagueOP
I'm using next canary.171, and PPR so I'm developing under some experimental versions so it could very well be related to either one of these things, but I'm leaning more towards
PPR since it is those serverless functions that are timing out and not the dynamically rendered ones (API Routes)PlagueOP
re-deploying fixes the issue, which was expected because it has something to do with the revalidation and
PPR functions, I strongly feel that.Im interested to see if anyone has any insight but be warned using Canary typically means wayyyyy less people able to help with issues.
@Jboncz Im interested to see if anyone has any insight but be warned using Canary typically means wayyyyy less people able to help with issues.
PlagueOP
Yeah, which is fine I don’t know what specifically caused it but I can almost guarantee it has something to do with how PPR handles revalidation specifically with revalidate tag cause as I mentioned revalidatePath worked fine