A utility billing worker crashes after consuming a Queue message bu…

Question

A utility billing worker crashes after consuming a Queue message but before deleting it. What happens when visibility ends, and what design duty follows?

Accepted Answer

The message becomes visible again, delivery count increases, and handlers must tolerate at-least-once redelivery (idempotent processing). — Delete is what completes Queue work. If the consumer crashes or never deletes, visibility ends and the message returns—delivery count goes up. Design handlers to be safe if they run twice. Streaming’s “read does not remove” is a different model.

Answer

The message is gone forever; Queue treats consume as permanent removal like a destructive read.

Answer

Streaming semantics apply: read never removes, so delete is ignored even if called later.

Answer

Events automatically dead-letters the message on worker crash without Queue involvement.

A utility billing worker crashes after consuming a Queue message but before deleting it. What happens when visibility ends, and what design duty follows?

Short Explanation

Full Explanation