Azure

The gateway timed out. Where did the payment go?

Retries, delivery counts and the queue Azure fills for you whether you read it or not.

What you'll learn

  • Why you never complete a message you cannot confirm
  • How delivery count and MaxDeliveryCount stop an endless retry
  • What lands in the dead-letter queue, and what to alert on
Azure 10 steps 32 seconds views

Was this useful?

Share

Understand it one step at a time

The short runs these in order in about 32 seconds. Here they are written out — pick any step to jump the short straight to it.

1 Step 1 of 10

11:42 — a customer pays

The order lands on the Service Bus queue at 11:42. A worker picks it up and calls out to the external payment gateway.

Frequently asked questions

What should you do with a message you can't confirm was processed?
Never mark it complete — an uncompleted message becomes available for redelivery instead of being silently lost, which is what lets retries recover from a transient failure like a payment gateway timeout.
What stops a bad message from retrying forever?
MaxDeliveryCount — once a message's delivery count reaches that limit it's automatically moved to the dead-letter queue instead of retrying indefinitely. The dead-letter queue is only useful if something alerts on its depth; left unread, it's the same as losing the message.

Free app · no app store

These are built for a phone

Every short is drawn at full portrait height, the shape a phone already is. Installed, it opens full-bleed with no address bar across the top — and the whole library reads offline.

How it works

Read deeper on Azure

Twenty seconds gets the shape of an idea across. These go into how it behaves in production.

More shorts

Get new posts by email

New technical articles, Azure AI and GitHub Copilot updates, and upcoming events. No spam, unsubscribe anytime.

navigate open