Flow-control recipes for Air Pipe pipelines: throttle with the delay action, retry with exponential backoff, branch with run_on_assertion, try/catch/finally recovery, and at_least quorum. Every endpoint is self-contained — no external services, databases, or managed variables required.
Call someone else's API and survive it. Declare which statuses count as success with expect_status, retry only what could plausibly succeed, send an Idempotency-Key so a retried POST cannot charge twice, and read a 404 or a 402 as data instead of an error. Self-contained: the examples call fixture routes on the same engine, so it deploys and curls with no external service, keys or database.