Queue safety / race conditions

Should this Yelp follow-up still send?

Put a reply or booking on the timeline, then test whether a queued message is cancelled before the delivery lock. The result is computed in your browser.

Scope: this checks cancellation logic, not message quality or Yelp API delivery. A production test still needs webhook timestamps, idempotency keys, and provider delivery logs.

Event timeline

Ready to test

Expected queue decision

Not run

Deterministic event log

Choose the event state and run the test.

Pass condition

Any stored reply or booking before send time cancels the queued follow-up. The worker checks again at the delivery lock.

Failure evidence

Keep the lead ID, event timestamp, queue ID, cancellation reason, and provider delivery ID. A screenshot alone cannot prove ordering.

Boundary case

If the reply arrives after the provider accepted the message, the queue cannot unsend it. Record that as a delivery race, not a cancellation failure.