Errors Not Appearing
Check your API key
Check your API key
Make sure it starts with
sq_pk_ and matches the project. Verify in Dashboard > Settings > API Keys.Enable debug mode
Enable debug mode
Add
debug: true to init(). Look for [squasher] messages in your console.Check network requests
Check network requests
Look for POST requests to
ingest.squasher.ai in the Network tab.202= accepted (check dashboard)401= invalid API key403= key doesn’t match project429= hit event limit
Log drain latency
Log drain latency
Vercel drains batch deliveries every 10-30 seconds. Wait at least a minute.
Sample rate
Sample rate
If
sampleRate is below 1, not all events are captured. Set to 1 for debugging.Minified Stack Traces
Production builds minify JavaScript. Upload source maps to get readable traces. See Source Maps.SDK Not Initializing
Missing env vars
Missing env vars
Make sure
SQUASHER_API_KEY and SQUASHER_PROJECT_ID are set in your deployment environment (not just .env.local).Wrong file location (Next.js)
Wrong file location (Next.js)
instrumentation.ts must be at ./instrumentation.ts or ./src/instrumentation.ts. No other location works.Next.js 14
Next.js 14
Enable the instrumentation hook:
experimental: { instrumentationHook: true } in next.config.js.Log Drain Issues
Vercel free plan
Vercel free plan
Custom HTTP log drains require Vercel Pro or higher. Use the SDK on Vercel free tier.
Railway false positives
Railway false positives
Railway drain uses keyword matching (“error”, “panic”, “exception”). Tune with the SDK for precise control.
Still Stuck?
Email support@squasher.ai with your project ID, SDK version, anddebug: true output.