Replies: 5 comments 4 replies
-
I am facing the exact same issue.
|
Beta Was this translation helpful? Give feedback.
-
Two things to consider:
|
Beta Was this translation helpful? Give feedback.
-
The issue is still there. I've moved away from axios (as an experiment) and I'm still getting double requests for app external API queries while fetching from |
Beta Was this translation helpful? Give feedback.
-
I experience something similar to this where I get two serverless executions for one client request. From what I can tell, it seems to be because Vercel triggers getStaticProps once to generate the json-file and once to generate the HTML-file. I've verified this by generating a unique id for each execution of getStaticProps and pass it as a prop to the page. Visiting the page directly shows one ID and navigating to it via next-link (using the json-file) will show another. Why the results of the getStaticProp execution can't be shared to generate both HTML and JSON I'm not sure but maybe it runs on different lambdas as rendering HTML requires more CPU and memory but this is pure speculation. |
Beta Was this translation helpful? Give feedback.
-
I am running into this issue as well. Just to summarize, I'm using |
Beta Was this translation helpful? Give feedback.
-
Hi lovely people, Vercel support team suggested me post here.
I've been getting a 2-3 duplicate requests from 2 different IPs a few milliseconds apart. This is consistent across all routes.
For example:
Doesn't happen locally - when I run
next dev
. Nor withnext build && next start
.We fetch data in
getStaticProps
only and are usingaxios
. Where could be the issue and how to resolve this?p.s.
this is causing unnecessary load on the backend + already exhausted my monthly log quote in a few days, causing Heroku go into
Error L10 (output buffer overflow)
mode. Halp!Beta Was this translation helpful? Give feedback.
All reactions