304/404 Warnings in Vercel Log
Unanswered
Braque de l'Ariège posted this in #help-forum
Braque de l'AriègeOP
Our Next.js application is deployed to Vercel and we are noticing numerous 304/404 warnings in the log.
The warning typically look like the following:
/_next/data/bundleId/work-with-us.json
/_next/data/bundleId/our-locations/las-vegas-nv.json
Those page loads fine if I navigate to the page.
client.com/work-with-us
client.com/our-locations/las-vegas-nv
Below is the code for the work-with-us page:
export async function getStaticProps() {
const graphQlRequest: Promise<WorkWithUsPageResponse | null> =
fetchWorkWithUsPageData()
const workWithUsPageData = await graphQlRequest
return {
props: {
data: workWithUsPageData?.data ?? null,
},
revalidate: 86400,
}
}
I saw a post mentioning adding fallback: 'blocking' but that appeared to be a workaround for a Next.js bug that is now resolved.
Any recommendations on how to resolve these issues? Are rewrites causing the issue?
The warning typically look like the following:
/_next/data/bundleId/work-with-us.json
/_next/data/bundleId/our-locations/las-vegas-nv.json
Those page loads fine if I navigate to the page.
client.com/work-with-us
client.com/our-locations/las-vegas-nv
Below is the code for the work-with-us page:
export async function getStaticProps() {
const graphQlRequest: Promise<WorkWithUsPageResponse | null> =
fetchWorkWithUsPageData()
const workWithUsPageData = await graphQlRequest
return {
props: {
data: workWithUsPageData?.data ?? null,
},
revalidate: 86400,
}
}
I saw a post mentioning adding fallback: 'blocking' but that appeared to be a workaround for a Next.js bug that is now resolved.
Any recommendations on how to resolve these issues? Are rewrites causing the issue?