Vercel
Next.js run time logs not showing #6812
-
QuestionI recently deployed two Next.js projects on my vercel account, and I noticed that the run time logs are always empty. I added some console logs statements in my code to check out some issues with my database in production environment, but I can't even see the logs |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
@kennyegun24 Can you share your project & the repository? |
Beta Was this translation helpful? Give feedback.
-
|
@versecafe , thanks for responding Here is my repository There happens to be an issue with data caching at the backend also.... In my local development server, each request queries the database for new data... in production mode, it just keeps sending cached data... here are images to show you what I mean
In the first screenshot, it happens to be fetched from my local server... I just deleted one object from my mongo db database, hence I only have 3 objects in therfe... Here is a snippet of my code to fetch from database |
Beta Was this translation helpful? Give feedback.
-
|
@kennyegun24 you're making a GET request with no param changes so it should be cached by default in production, you can try something like export const dynamic = 'force-dynamic';in the routes you want to always rerun or instead use cache headers like this to have set revalidation time {
"Cache-Control": "max-age=300, s-maxage=300, stale-while-revalidate",
} |
Beta Was this translation helpful? Give feedback.
-
|
@versecafe thank you, the caching has stopped Thank you for resolving my issues 🙇 |
Beta Was this translation helpful? Give feedback.
@kennyegun24 you're making a GET request with no param changes so it should be cached by default in production, you can try something like
in the routes you want to always rerun or instead use cache headers like this to have set revalidation time
{ "Cache-Control": "max-age=300, s-maxage=300, stale-while-revalidate", }