Results for “retry”
7 skillsn8n-error-handling
Makes n8n workflow failures loud, structured, and recoverable by wiring per-node error outputs, retry logic, error-trigger workflows, and proper HTTP response shapes.
5.7k · bundle
resiliency-circuit-breakers
Trigger: circuit breaker, exponential backoff, jitter delay, connection timeout, API retry. Scope: Client request resiliency, API retries, fault isolation. Boundary: Excludes visual state loading skeletons.
1 · bundle
076-api-0a2a6d49
Implements scheduled handlers for Cloudflare Workers, covering cron triggers, retry control, multiple schedules, workflow integration, and testing.
7 · bundle
More results
webhook-setup
Set up webhook receivers with signature verification, idempotent event processing, retry handling, and dead letter queues for reliable event-driven integrations. Use when the user requests webhook setup or provides relevant inputs for this workflow.
159
unstick-pr
Recover a PR whose head SHA disagrees with its branch ref (webhook desync). Force-push and close+reopen rarely fix it — recreate the PR.
1 · bundle
api-integration
Integrate with external APIs using REST clients, webhook consumers, SDK wrappers, and polling patterns with proper authentication, error handling, and retry logic. Use when the user requests api integration or provides relevant inputs for this workflow.
159
fallback-chains
Layer alternative channels / scrapers / data sources with explicit fall-through, where each rung covers a different failure mode. Use when interacting with the world (sending a notification, fetching from a third party, detecting a state change, authenticating) and the single canonical path could fail in known ways. Distinct from retrying — retries handle transient failures; fallback chains handle modal ones (channel down, API gone, cookie expired). Three layers tops; the terminal rung is loud.
6