Comments (5)
Ok... I found the real problem.
The href pointing to the route should have been like this: href="https://mysite
instead of href="https://www.mysite
^^^ for some reason adding the www didn't work.
Must have been something in the settings of the site at Vercel, or something from Godaddy... not sure, but I found the problem by accident when typing the route manually on the browser.
from next.js.
How long does it take for the email to be sent? It sounds like you might be hitting the default serverless execution limits, which can be configured via maxDuration
: https://vercel.com/docs/functions/configuring-functions/duration
If you're still running into troubles, I'd suggest opening a Vercel support ticket or community post, as GitHub issues are specifically for bugs or feature requests within the framework regardless of where it's hosted.
from next.js.
Thanks..
According to the Vercel information the max duration is already 15 seconds if I am reading it properly.
I also put it on the route.js to increase it to 10 according to the data you linked. Not sure if I am doing it properly.
Anyway, the error remains.
I have posted it on the community, but of course haven't gotten an answer and I am looking elsewhere, and I saw people with similar issues and didn't see an answer there either.
I will try to open a ticket at Vercel... . and wait... hopefully I get some feedback soon.
from next.js.
Thanks..
According to the Vercel information the max duration is already 15 seconds if I am reading it properly.
I also put it on the route.js to increase it to 10 according to the data you linked. Not sure if I am doing it properly.
Anyway, the error remains.
I have posted it on the community, but of course haven't gotten an answer and I am looking elsewhere, and I saw people with similar issues and didn't see an answer there either.
I will try to open a ticket at Vercel... . and wait... hopefully I get some feedback soon.
Can you clarify what the error is?
from next.js.
My goodness..
It works now? kind of, but for some reason it sends 3 emails instead of 1.
The code is the same, other than adding the timing that you suggested, but I tested it yesterday and didn't do anything either.
Suddenly, today, the page redirects and sent 3 emails instead of just 1.
The people from Vercel say they don't help at code level problems and just to ask the community, which I have asked, and searched for answers, and didn't find anything.
Anyway... since apparently the code is taking the actions it should, I will open another question in the community asking why would the code repeat the action of sending emails so many times.
I got to say, this is "weird" how the code seems to suddenly execute.
from next.js.
Related Issues (20)
- Critical bug in NextJS v14.2.7 - renders page source code instead of components HOT 1
- Next v14 Double Render HOT 1
- Turbopack: `resourceQuery` from import isn't passed to loaders HOT 1
- Docs: Documentation incorrectly says database calls will opt in to server side rendering by default
- Docs: geolocation is confusing (w/vercel) - why is req.geo only available on middlewere
- Error: headers was called outside a request scope, when using Authjs v5.0.0-beta.19 and next dev --turbo
- Import .ts files in Instrumentation HOT 1
- Duplicate className in deploy-button.tsx causing Tailwind CSS error in with-supabase example
- [SWC] [Webpack] [Tree Shaking] combines exports of modules and constants across pages HOT 1
- Unexpected behaviour of app router when deployed to vercel
- [Next/Jest] debugger statement is ignored in chrome debugger
- Code imported inside instrumentation.ts can't mutate imported modules
- @svgr/webpack integration crashes on render inside server component (undefined runtime error) HOT 1
- Favicon.ico link not using `sizes="any"`
- i18n in next.config.js introduces significant latency in App Router HOT 3
- Turbopack fails to compile code referring to `shiki` though Webpack can compile it HOT 1
- BeforeInteractive script not firing after calling notFound() function HOT 3
- Next.JS 15 RC freezes occasionally when forwarding (`rewrites()`) requests to FastAPI endpoint
- pages router global _error.tsx is triggered instead of app router global-error.tsx when force-static page used
- Unexpected Behavior: Server Side Function running twice HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from next.js.