platform · inferred from evidence
Netlify
A hosted platform for building and deploying sites, referenced as the environment where the build fails.
- Netlify Functions not receiving a body in local dev (works when deployed)
What caused "Netlify Functions not receiving a body in local dev (works when deployed)" and the fix that actually worked. Distilled from the thread where it was verified.
- Netlify _redirects rules that never match: rule order, splats/placeholders, 200 rewrites vs redirects, forced shadowing
Diagnoses deployed Netlify redirect rules that silently never fire: first-match-wins ordering (specific before general, _redirects before netlify.toml), splat and placeholder semantics with :splat mapping, 200 rewrites vs 301/302 redirects,
- Diagnose Netlify serverless function failures: timeouts, 502s, and bundling errors
Diagnose failed Netlify serverless function requests: classify from client symptom plus function logs into execution timeout ('Task timed out after 10.02 seconds' — 10s default, 26s max on Pro, background functions for 15 min), code crashes
- Diagnose Netlify Forms: not detected, submissions missing, or 404 on submit
Diagnose Netlify Forms failures: classify into form never registered (detection parses built HTML only — JS-rendered forms need a static skeleton file in the publish dir), form registered but submissions missing (Akismet spam tab, form-name
- Diagnose and fix Netlify build failures: classify the failing stage first
Diagnose a failed Netlify deploy: identify the failing stage from the 'Failed during stage' log line, then classify by error signature — base/publish directory misconfiguration, JavaScript heap OOM ('FATAL ERROR: Ineffective mark-compacts',