ApiSkills

HTTP & Networking · 10 min

Resilience: timeouts, retries, redirects, batching

Real networks fail. Practice the settings that make an integration robust.

These endpoints let you deliberately trigger the conditions that break fragile workflows, so you can configure for them.

endpointwhat it does
/playground/response?status=429&delay=1500Return any status after any delay
/playground/timeout?delay=5000Sleep, to practice n8n's Timeout setting
/playground/redirect?n=3A chain of redirects to follow
/playground/batchSend an array of sub-requests, get an array back
/playground/headersSee your headers exactly as received

Every delay, count, and size is capped server-side, so you can experiment freely without ever taking the sandbox down.

  • A 429 means "rate limited" — the correct response is to back off and retry, not hammer.
  • Set a sane Timeout in n8n so a slow endpoint fails fast instead of hanging your workflow.

Tip · Combine these: point n8n at /playground/response?status=503, enable Retry On Fail, and watch it recover.