Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On demand revalidation not working in basic example on vercel #54640

Closed
1 task done
jdgamble555 opened this issue Aug 27, 2023 · 2 comments
Closed
1 task done

On demand revalidation not working in basic example on vercel #54640

jdgamble555 opened this issue Aug 27, 2023 · 2 comments
Labels
bug Issue was opened via the bug report template. locked Runtime Related to Node.js or Edge Runtime with Next.js.

Comments

@jdgamble555
Copy link

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Vercel, NextJS Canary

Which area(s) of Next.js are affected? (leave empty if unsure)

App Router, Middleware / Edge (API routes, runtime)

Link to the code that reproduces this issue or a replay of the bug

https://github.com/jdgamble555/next-isr-test

To Reproduce

https://next-isr-test-nine.vercel.app/

Describe the Bug

I run the revalidatePath('/'); function, which seems to return without problems, and my app directory path (just the default '/' directory) does not get revalidated.

Potentially related to:

Expected Behavior

It should revalidate.

Which browser are you using? (if relevant)

Chrome, same on any browser

How are you deploying your application? (if relevant)

Vercel

@jdgamble555 jdgamble555 added the bug Issue was opened via the bug report template. label Aug 27, 2023
@github-actions github-actions bot added the Runtime Related to Node.js or Edge Runtime with Next.js. label Aug 27, 2023
@jdgamble555
Copy link
Author

jdgamble555 commented Aug 29, 2023

closing, as fixed when changed from get to post method

@github-actions
Copy link
Contributor

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template. locked Runtime Related to Node.js or Edge Runtime with Next.js.
Projects
None yet
Development

No branches or pull requests

1 participant