Infrai queue developer guides
Every Infrai queue guide in one place: quickstarts, production patterns, error resolution, and operations runbooks verified against the live API.
answers
- Duplicate jobs in an at-least-once queue: the idempotency key that fixes it
- Delayed retries beyond 7 days: chaining hops on a job queue
- Cleanup jobs that retry themselves: Node queue, DLQ, redrive
- Message too large and JSON that won't parse: fixing malformed queue payloads
- Background jobs in Node: create a queue, run a worker, ack and nack
- Job keeps coming back? Three causes of endless queue retries
- Exponential backoff for failed jobs when your queue only retries three times
- Cron or a job queue? Picking one for file, email and webhook work
- Your push subscriber is returning 429: what the queue does next
- Long-running jobs and the 15-minute wall: checkpoint instead of extending
- Batch enqueue in Node: 100 jobs per publish call, then a paced worker
- Choosing a queue for user reminders when the send can fail
- DLQ redrive or a Postgres retry table: which one is cheaper to run
- The webhook callback queue pattern: delay, retry, dead-letter
- Exponential backoff for failed queue jobs: which curve, and where the wait lives
- Choosing a background job queue for a multi-tenant Node.js SaaS
- A simple queue retry policy in Node: backoff without a delay parameter
- A per-user reminder backend: schema, delay budget, delivery
- Reminder scheduling for SaaS: cron, queue, or a notifications API
- Cron or queue for cleaning up old records once your Node app has replicas
- Scheduled S3 cleanup jobs with a queue, retries and a DLQ
- Daily report emails: when cron alone is enough, and when it isn't
- Reminder notifications that send exactly once: cron, Postgres due_at, queue
- BullMQ, SQS or a managed HTTP queue: what each one makes you responsible for
- Cheap webhook task processing when the downstream API is rate limited
- Cheapest queue for rate-limited webhook fan-out: US and EU options compared
- Your coding agent scaffolded Redis and BullMQ again: the managed swap
- Cloud cron or a queue when the API you're batching against is rate limited
- A once-a-minute cron tick as your outbound rate limiter, in Node
- Nightly pending-webhook sweep: one cron tick, batched publish, one worker
- Past the serverless time limit: cron enqueues, a worker does the long job
- Delayed webhook retries: cron sweep, message queue, or both?
- Per-event delayed tasks: why a cron row per order doesn't scale
- Daily report emails: one cron run, or a queue job per tenant?
- Daily report email to a huge recipient list: cron trigger plus queue fan-out
- 40 report emails failed last night: rerun the job or work the DLQ?
- FIFO or standard queue? Duplicate handling for a small SaaS
- Reminder in three days: delayed queue message or a cron sweep?
- Is durable execution overkill when you only need retries and a DLQ?
- Nightly stale-upload deletion, paced against your storage provider's limit
- Scheduling a webhook follow-up an hour later: per-event job or one ticker?
- What a managed cron plus queue stack really costs a side project
- Push queue deliveries into Express or Fastify: the URL is the credential
- Cleaning up expired sessions and tokens with a Node cron and queue
- Express to worker: the three idempotency keys a background job needs
- A Node webhook worker with retries, a dead-letter queue and redrive
- Scheduled Postgres log cleanup in Node: cron plans, queue batches, safe replays
- Timezone-correct user reminders with a cron sweep and delayed queue messages
- Push subscription or polling consumer: which one retries failed jobs better
- Do you need a public HTTPS endpoint for cron and push queue delivery?
- Building the Node endpoint that receives queue push deliveries safely
- Queue or cron for failed webhook retries? Two inequalities decide it
- Triaging a dead-letter backlog after a rate-limited API run
- Push or poll when your queue consumers are serverless functions
- Rate-limited email sending: putting a queue in front of Resend, Postmark or SES
- Rate-limited jobs: which backend actually bills you for waiting?
- Node.js worker at concurrency 1: batch enqueue, paced retries, idempotent jobs
- Backpressure for a scheduled cleanup that calls a rate-limited API
- Node.js reminder fan-out: batch publish, paced workers, provider caps
- One throttled customer shouldn't stall your whole webhook queue
- Retrying failed jobs: a Postgres jobs table and cron, or a queue?
- Retrying failed reminder notifications without notifying anyone twice
- Cheapest scheduled cleanup in Node: when Postgres alone beats a queue
- Retrying failed webhooks: delayed republish, cron sweep, or push retries
- Deleting user data after 30 days: a webhook-triggered cleanup you can prove ran
- Pruning 40M Postgres rows on a schedule with a self-feeding queue
- Nightly data cleanup in Node: a cron-hit endpoint that fans out to a queue
- A dead-letter redrive runbook for small Node.js SaaS teams
- Daily and weekly reminders in local time: one cron job per timezone
- A token bucket in the queue worker: Node example with 429 penalties
- Cron hit the 900-second wall and your worker has no public URL
- Why your delayed reminder never fired, and how to find out
- Reminder fan-out throttled: 429 backoff, dead-letter and redrive in Node
- Push subscription or pull consumer? Where the webhook rate limit has to live
- Exponential backoff and DLQ redrive for failed webhooks in Node.js