Vercel
Cost
Performance
Stability
maxDuration > 60 s on non-streaming function
Part of the Caching & cost check · fix arrives as a guide
What it is
A function is configured with maxDuration above 60 seconds without streaming a response.
Why it matters
You are billed for the duration, and a long ceiling means a stuck request bills for the whole window instead of failing quickly. Without streaming the user also sees nothing until it completes.
How to fix it
Lower maxDuration to slightly above the genuine p99 for that route, and move genuinely long work to a queue that returns a job id immediately. Reserve long durations for streaming responses.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.