Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Logistics Renewal Deadlines: When Should Failed Webhook Jobs Use a Delayed Queue or Cron?

Short answer: use a delayed queue when each failed webhook job needs its own retry time and audit trail; use cron to run a bounded redrive or reconciliation sweep when a little extra latency is acceptable and the database already owns retry state. A public HTTPS endpoint is for receiving the webhook or a cron callback, not for exposing a private retry worker. For a logistics system, the decision…

When dealing with failed webhook jobs, there are two main options: using a delayed queue or employing a cron schedule. The choice depends on two critical factors: latency tolerance and the need for an individual retry time and audit trail for each job.

A delayed queue is ideal when each failed webhook job requires its unique retry time and audit trail. This approach keeps eligibility attached to the individual message, allowing the worker to record the attempt, calculate the next eligible time, and defer the job while other tasks continue. The retry clock in this case belongs to the failed delivery itself, rather than a periodic scan of all outstanding deliveries.

Cron, on the other hand, is a control-plane mechanism that wakes up on a schedule, calls a public HTTPS endpoint, or starts a process to select due rows. While it can be used for a bounded redrive, dead-letter review, or reconciliation pass, it does not provide an idempotency ledger or evidence that a specific attempt owns a particular effect.

The decision on which method to use should primarily hinge on the business deadline. A reminder to renew a carrier contract may be necessary before the deadline, but sending the same reminder multiple times is preferable to sending it late. Latency is a crucial consideration, but the retry mechanism must ensure that one delivery failure does not result in two business effects.

To implement this effectively, it's essential to treat every attempt as a durable entity, record every state transition with an audit trail, and maintain idempotency. The implementation can be kept simple, but the correctness argument cannot. The cost of latency when failed webhook jobs wait in a delayed queue or cron schedule varies.

A delayed queue preserves eligibility with the individual message, allowing the worker to record attempts, calculate next eligible times, and defer jobs without interrupting other work. Cron, being a control-plane mechanism, is useful for bounded redrives, dead-letter reviews, or reconciliation passes but lacks an idempotency ledger or evidence of a specific attempt's ownership of a particular effect.

In conclusion, the choice between a delayed queue and cron schedule depends on the specific logistics system's requirements and constraints. A delayed queue is suitable when retry timing is part of the delivery contract, failures are unevenly distributed, or operators need to inspect jobs without reopening the entire backlog. Cron is preferable when retry volume is modest, a scan is already part of the database design, and the deadline can tolerate the next scheduled run.

However, neither method guarantees exactly-once delivery, and proper evidence and retention rules must be in place to ensure that the distinction between a reminder sent, attempted, or made durable at the receiver is transparent and stable.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

From sleep(5000) to a real UI check: five tests for desktop automation

A desktop automation can pass in a demo and still fail on a real workstation. Fixed delays, small layout changes, and retries that repeat the wrong action are common reasons.

  • Test flow when window and control are already visible
  • Introduce artificial delays to mimic slower machines
  • Render target unavailable to trigger failure scenario

QR Code Generator: Why Half My Printed Tickets Refuse to Scan

Last month I printed 250 tickets for a company offsite. Each ticket carried a QR code pointing at our check-in form. On the morning of the event, roughly a third of them refused to scan. The phone camera would focus, hesitate, and give up. No error message, nothing. The codes looked perfect on my screen, so I blamed the print shop.

  • Reporter printed 250 tickets with QR codes for event
  • Initial border parameter set to 0, causing scanning failures
  • Fixed by setting border parameter to 4 for quiet zone

How to Write a Creator Bio That Gets Follows (2026): Score Your Drafts, Keep One Call to Action, Cut Unproven Claims

Full disclosure: I built a bio-scoring tool on Capafy, so I'm biased. Everything below works with a notes app and fifteen honest minutes. You don't need the tool to use the method. TL;DR Your profile bio is the last thing a viewer reads before they decide to follow, and most creators write it once and forget it.

  • Bio's purpose is to convince viewers to follow a creator
  • Include only verifiable facts like posting frequency and credentials
  • Score drafts 0-10 on clarity, credibility, and call to action

More from Sunday 22 November →