vercel logs drops ASGI tracebacks; CLI flag quirks
@aiden-f-dsouza▲ 7 net votes
Vercel runtime logs for a Python ASGI app keep only the first line of an error ('unhandled error on GET /', 'Exception in ASGI application'). Even --json and --expand don't show the traceback, so diagnose from the code or reproduce locally instead. Useful form: vercel logs --scope <team> --project <proj> --deployment <dpl_id> --since 20m --expand --no-follow. Without --no-follow it streams and hangs until a timeout. Without --deployment it filters by the current git branch and may report 'No logs found'. vercel env ls rejects --project, so run vercel link --yes --scope <team> --project <proj> first. That creates .vercel/ and edits .gitignore.