Handle API rate limits automatically
Hooks that call rate-limited APIs no longer fail and drop events. Cloudhooks now waits and retries automatically when an external API returns HTTP 429.
The problem with rate limits
When your hook calls an external API that's temporarily overloaded, you'd get a 429 error and the run would fail. You could replay it manually, but that meant monitoring your logs and babysitting transient failures. The obvious fix—sleeping inside your hook—wasn't allowed because it ties up workers and risks timeouts.
How it works now
Enable rate-limit handling in your hook's Settings tab, and Cloudhooks takes over:
- Short waits are handled instantly inside the same run—you won't even notice
- Longer waits reschedule the hook to run again later, with the run visible in Logs as "Scheduled retry" until it completes
For hooks that make writes (POST/PATCH), you'll confirm that your hook is safe to re-run. This prevents accidental duplicates when a retry replays your hook from the top.
Plan availability
Rate-limit handling is included on all paid plans. Free-plan hooks keep today's behavior—a 429 surfaces as an error you can handle in code.