I’m not sure when it happened (i.e. which deployment) but my NextJS (15.3.1) project no longer shows request details in my runtime logs:
As shown above, the requests are logged, but there’s no additional info/messages available via the Logs accordion dropup. Just a No logs found for this request message for all logs.
Does anyone have any idea what may be causing this issue? I can’t find any changes/commits in my app that could cause this.
Many thanks.
Not every request will have something to show in the logs. Is this a function that normally does log something there?
Thanks for your reply.
The Vercel dashboard was showing logs for most (~80%) requests to my app/project up until a few weeks ago. Now, nothing at all:
I’m having a hard time pinpointing what changed. i don’t see any code changes I made that might cause this, so I can’t figure out where to start debugging this issue.
Any ideas?
Hi @colinwilson, I see what you mean. Can you put some logs in a new route (very basic route just with logs) and try to run it when using the Live mode in the Logs page? This way we can confirm that the issue is reproducible.
I see you are on the Hobby plan so logs are not persisted for more than an hour.
From our plan comparison page:
1 hour of logs and up to 4000 rows of log data
Hi @anshumanb ,
I’m not 100% sure what you mean by, “put some logs in a new route”?
I tried adding a basic route /media-library with user session calls and using live mode. Still nothing I’m afraid:
Any Ideas? I’m completely stumped as to why the logs just stopped.
Hi @colinwilson, thanks for confirming. Let me check with our team internally about this.
Hi @colinwilson
We’re grouping multiple datapoints together to build the request log. When using Live Mode it could be that you only see the initial data from middleware (your first screenshot) - if you do a console.log in the middleware itself it should show up but this could be delayed by a few seconds (needs another refresh) to show up.
If you’re logging in the Vercel Function itself (like /media-library) it should also show up and also can be delayed by up to ~5seconds in the worst case.
Do you see the console.log for “older” logs or is everything empty?
If this is the case, I’d need a projectId or domain so we can look into this further!
Thank you!
Thank you @anshumanb .
Hi @tobias ,
Do you see the console.log for “older” logs or is everything empty?
No I’m afraid. Empty.
I’ll message you my projectId.
Thanks for taking the time to help me.
EDIT: Couldn’t find a way to message you my projectId. Is it safe to post it here in the thread?
I’ve sent you a DM @colinwilson. You can safely send this information there.
Hi @colinwilson, we’re checking the project information. We will keep you posted here when we have an update.
Hi @colinwilson
I looked at your data and everything seems normal to me. It seems like you’re not doing any manual console.logs and function invocations also appear when they are triggered.
Are you missing some requests to the edge network that served static content? This is something we have not shown before but when there is a middleware in front we should - this seems like a bug (not showing the ISR cache result)
Does this answer your question?
Hi @tobias ,
Thanks for taking the time to look at this for me.
function invocations also appear when they are triggered
Is it normal to not have any details in the logs for NextJS function invocations (or does it depend on the function type?)?
On one of my other projects (node) I see detailed info/messages for each function invocation.
I swear I was getting the above type info before on this project (but obviously not anymore). I’m not sure If I did something to change that.
You only see logs if there was a invocation, maybe by upgrading Next.js some pages are now build statically - so only a middleware is invoked and then the static content served (we’re sometimes missing this data in some cases sadly, working on it!)
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
