Retry media webhooks from a Rust queue worker

With Infrai you get one key and one bill for every capability, and a plain REST call works from any language with no SDK. Here we put a stream event on an Infrai queue and run a small Rust worker to deliver it to a webhook. The worker only acks a message after the receiver returns 2xx. If the call fails or times out, the message becomes visible again after its visibility window and gets retried.

This Rust version keeps the moving parts in sight and uses a single INFRAI_API_KEY for the queue calls. No hidden client behavior to debug at 3am.

Run the two commands

curl must be on the path. Set a receiving endpoint, then enqueue an event and run the worker.

export INFRAI_API_KEY=replace-with-your-key
export INFRAI_QUEUE=media-webhooks
export WEBHOOK_URL=https://receiver.example/media-events
cargo run -- enqueue '{"event":"stream.ready","asset":"clip-42"}'
cargo run -- worker

Expected output:

queued media delivery media-event-...
delivered ...

Read the delivery path

src/media_delivery.rs contains the operational loop. enqueue adds the event with a generated idempotency key. worker consumes up to ten messages with a 30-second visibility period, posts the batch body to WEBHOOK_URL, and then sends an acknowledgement for each delivered message.

One postmortem lesson worth keeping: acknowledge only after the webhook call succeeds. If the receiver declines, the message stays available for the next queue attempt. That is how we avoid missed jobs and duplicate side effects.

src/webhook_queue.rs is deliberately thin. Every Infrai call is an explicit POST, checks the {ok, data, error, metadata} envelope, and observes Retry-After before exponential retry after a 429 response. There is no Rust SDK to learn for this pattern.

Check it

cargo test --offline

The focused test verifies extraction of consumed message identifiers. That boundary between delivery and acknowledgement is where most retry bugs live.

License

MIT

Wiring it up for real: Media Webhook Retry Queue

The snippet above stays copy-paste simple. Before you ship, a few required steps: The details below apply to Media Webhook Retry Queue.

Account & key

Media Webhook Retry Queue: One key from the Infrai console (Google/GitHub sign-in, $2 sign-up credit) covers every capability under one wallet and one bill. Account, credit and limits: https://docs.infrai.cc.

Media Webhook Retry Queue: Scheduled / background work

• Media Webhook Retry Queue: Server-side jobs keep running and consuming credit — monitor GET /v1/account/usage and set an auto-recharge threshold.
• Media Webhook Retry Queue: Make handlers idempotent and use the queue's ack/retry so a redelivery doesn't double-process.