Urgent.News

What's breaking now, across thousands of outlets.

Tuesday, 10 November 2026 Reading Room

Tech

Common Causes of Delayed or Missed User Reminders: Replaceable Cron Delivery

Common Causes of Delayed or Missed User Reminders: Replaceable Cron Delivery Short answer: the common causes of delayed or missed user reminders are a paused cron job, an unavailable public callback, or a run longer than 900 seconds. Keep the cleanup trigger, durable message, and user-facing delivery behind replaceable boundaries. A queue plus a realtime channel gives the failure somewhere to…

dev.to ·

The article discusses the common causes of delayed or missed user reminders, specifically focusing on replaceable cron delivery. It identifies three main failure boundaries: a paused cron job that does not backfill missed triggers, an unavailable public callback due to an internal hostname or private network address, and a 900-second timeout limit for a single cron execution.

To address these issues, the author suggests keeping the cleanup trigger, durable message, and user-facing delivery behind replaceable boundaries. The recommended solution involves using a queue plus a realtime channel, ensuring idempotency, and employing a stable idempotency key for retrying deliveries. The author also highlights the importance of splitting the cleanup sweep into queue messages to make the process retryable while emphasizing the need for a clear contract between the cleanup sweep, queue, and realtime delivery.

Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The limit you configured is not the limit it applies

An agent that pays for things needs a limit: a maximum price per call, a payee you expect, sometimes a list of networks and tokens you trust.

  • Limit applies to signed payment, not quote
  • Dishonest seller issues varying quotes and demands
  • Successful SDKs enforce limit on requirement being signed

·dev.to

Snapping a tap to a real corner: building a LiDAR tape measure for iPhone

When you tap the screen to start a measurement, you are not tapping the corner of the table. You are tapping a pixel, and that pixel sits on a ray that leaves the camera and hits something .

  • Users tap screen to initiate measurement, not table corner.
  • iPhone app uses depth and image data for measurement.
  • RANSAC identifies up to three planes for accurate measurement.

·dev.to

Centreon API tokens inherit the union of access groups

Centreon API tokens inherit the union of access groups Centreon provides monitoring, configuration, and API access through several interfaces.

  • Centreon API tokens inherit access rights from multiple user access groups
  • Authentication tokens, CMA tokens, and poller tokens are distinct credentials
  • Centreon users can belong to several access groups, combining their rights

·dev.to

Why does my error tracker show one bug as hundreds of different errors?

Originally published at runheed.com . Error trackers group repeats of a bug by a fingerprint, usually built from the error type, the message and where it was thrown.

  • Error trackers group bugs using a fingerprint based on type, message, and location.
  • Varying values like user IDs or timestamps create new fingerprints for each instance.
  • Removing changing values and excluding line numbers clarifies distinct bug identification.

·dev.to

Introducing Quantum Frequency Modulator: Next-Token Prediction Without Attention

This single-file PWA that turns words into noise frequencies, collides them in a lattice, and drafts text from the resulting signature — an experiment in frequency-domain next-token prediction as an…

  • Quantum Frequency Modulator (QFM) generates text via frequency-domain next-token prediction
  • Eliminates attention matrices, uses lattice structure for frequency collisions
  • In-browser process with real-time visual/audio feedback for prediction

·dev.to

Alerting on cron and background jobs that never ran, hung, or did nothing (in 6 languages)

Our HTTP alerting was in good shape. 500s, slow endpoints, error rates: all covered. Yet the incidents that hurt most kept coming from somewhere else: The 02:00 invoice job never started , because the…

  • RunSignal monitors cron and background jobs across 6 programming languages
  • Provides metrics for success, failure, cancellation, duration, and handled items
  • Ensures alerting even if processes die or do nothing

·dev.to

More from Tuesday 10 November →