| name | vercel-advanced-troubleshooting |
| description | Advanced debugging for hard-to-diagnose Vercel issues including cold starts, edge errors, and function tracing.
Use when standard troubleshooting fails, investigating intermittent failures,
or preparing evidence for Vercel support escalation.
Trigger with phrases like "vercel hard bug", "vercel mystery error",
"vercel intermittent failure", "difficult vercel issue", "vercel deep debug".
|
| allowed-tools | Read, Grep, Bash(vercel:*), Bash(curl:*), Bash(jq:*) |
| version | 1.18.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","vercel","debugging","advanced","troubleshooting"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
Vercel Advanced Troubleshooting
Overview
Diagnose hard-to-find Vercel issues: intermittent cold start failures, edge function crashes, region-specific behavior, function bundling problems, and serverless concurrency issues. Uses systematic isolation, request tracing, and Vercel-specific debugging techniques.
Prerequisites
- Vercel CLI with access to production logs
- Familiarity with
vercel-common-errors (standard debugging)
curl and jq for API inspection
- Access to deployment inspection tools
Instructions
Step 1: Request-Level Tracing
curl -v https://yourdomain.com/api/endpoint 2>&1 | grep -E "x-vercel|cf-ray|age|cache"
Step 2: Cold Start Investigation
let coldStart = true;
const initTime = Date.now();
export default function handler(req, res) {
const isCold = coldStart;
coldStart = false;
const handlerStart = Date.now();
res.setHeader('x-cold-start', String(isCold));
res.setHeader(, (handlerStart - initTime));
res.({
: isCold,
: isCold ? handlerStart - initTime : ,
: .() - handlerStart,
: process..,
});
}