# Queue a delayed or retried HTTP call

> Queue a delayed or retried HTTP call: 0 companies fully do it, 3 with a limit, 21 carry the tag. Every listing in Event delivery & webhooks with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/webhooks.queue-http-job/
- Markdown: https://www.anchorterminal.com/niches/webhooks.queue-http-job/index.md (~950 tokens)
- Slim: https://www.anchorterminal.com/niches/webhooks.queue-http-job/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/webhooks.queue-http-job/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 3 | 21 | 11 | 5 |

## What counts as done

The call is accepted once (deduplicated on a key), delivered after the delay, retried up to the set count and no more, in order when a FIFO queue is chosen, with queue depth readable.

How agents ask for it: run this job in the background; retry this call until it works; call this in ten minutes; process these one at a time

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Amazon EventBridge (Amazon Web Services, Inc.)**: Custom Event Bus entries deduplicate on DeduplicationId for 5 minutes and FIFO subscribers keep order per event group, but delayed one-off HTTP jobs need Scheduler, and queue depth is not readable on the bus.
- **Hookdeck (Hookdeck Technologies Inc.)**: Events queue per destination with retry counts and dedup windows, but no delayed delivery or FIFO ordering was found in the pages read.
- **Upstash QStash (Upstash, Inc.)**: Deduplication holds 10 minutes, Upstash-Delay defers, Upstash-Retries caps retries and queues deliver FIFO, but the lag reading is reported inaccurate (#102, open) and the pricing pages disagree on whether retries are billed.

- not this job: 402cron (Georgi Kalchev (operator, a named person; no company named)): No one-off delayed jobs, dedup key on enqueue, FIFO or queue depth.
- not this job: Ably (Ably Realtime Ltd): AMQP queues carry channel messages to consumers; there is no delayed HTTP job with retry count and dedup.
- not this job: Centrifugo (Centrifugal Labs LTD): No HTTP job queue.
- not this job: Convoy (Frain Technologies Inc.): No delayed one-off HTTP jobs or queue depth; it is a webhook gateway.
- not this job: Hook0 (FGRibreau SARL): No delayed jobs or queue depth.
- not this job: PubNub (PubNub Inc.): No HTTP job queue.
- not this job: Pusher Channels (MessageBird UK Limited): No HTTP job queue.
- not this job: Svix (Svix Inc.): No delayed HTTP jobs or queue depth.
- not this job: Webhook Relay (AppScension Ltd): No enqueue call with a delay, dedup key or queue depth; durable retries apply to forwarded webhooks.

## What stops agents finishing

- every retry billed as a message with no cap
- no ordering, so dependent jobs run out of order

## Around it

Before: webhooks.receive-reliably. After: database.write-record.

## Where this comes from

Weight 11 of 100 in Event delivery & webhooks: 5 of 40 accounts; four are older QStash GitHub issues (2022 to 2024) that may be fixed

As data: https://www.anchorterminal.com/api/v1/use-cases/webhooks.queue-http-job.json, or the MCP tool get_use_case with id webhooks.queue-http-job. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
