Debugging scenarioHard~12 minAzure Production Incident Debugging Essentials / 12 of 15

Interview question

A Service Bus worker produced the same external side effect twice. The second attempt has the same MessageId, DeliveryCount 2, and a lock-renewal failure after the provider call succeeded. How would you diagnose, contain, and repair it?

Debug duplicate Azure queue processing after lock loss

Diagnoses duplicate processing from Azure Service Bus lock loss or Storage Queue visibility behavior without repeating generic idempotency theory.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

For a Service Bus case, I start with one duplicated side effect and inspect MessageId, delivery count, lock-lost or renewal events, settlement outcome, worker instance, and the external provider reference. If delivery count increased after the provider succeeded but before CompleteMessageAsync succeeded, this is redelivery of the same message. I pause unsafe consumption and reconcile the provider before allowing another effect.

Full answer below

Practice focus

Azure delivery evidence, lock loss, settlement, redelivery, provider idempotency, reconciliation, and failure-injection proof.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
A worker can finish the business side effect yet fail before message settlement or durable completion. Redelivery is correct broker behavior, so duplicate safety must exist at the side-effect boundary.
For a Service Bus case, I start with one duplicated side effect and inspect MessageId, delivery count, lock-lost or renewal events, settlement outcome, worker instance, and the external provider reference. If delivery count increased after the provider succeeded but before CompleteMessageAsync succeeded, this is redelivery of the same message. I pause unsafe consumption and reconcile the provider before allowing another effect.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
The consumer stores a durable operation record and reuses the provider idempotency key, so redelivery returns the known outcome instead of charging or sending twice. Lock duration and renewal fit measured work, and long processing is split or checkpointed rather than hoping the lock survives. Service Bus duplicate detection can suppress repeated sends with the same message id inside its configured window, but it does not prevent redelivery after lock loss and does not replace consumer idempotency.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
I prove the repair by forcing provider success followed by lock loss or failed settlement, then observing a higher delivery count with only one external effect. Metrics join delivery count, lock renewal, settlement failures, active-message age, duplicate-key hits, and provider responses. Storage Queue uses visibility timeout and dequeue evidence instead of Service Bus lock events, so the diagnostic names the deployed broker. The portable idempotent-consumer drill owns the failure pattern; this incident owns Azure delivery evidence and recovery controls.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Assuming every duplicate effect came from broker redelivery.
Replaying messages before checking external provider state.
Completing the message before the durable local transition.
Treating a longer lock timeout as a substitute for idempotency.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Cannot explain at-least-once delivery.
Has no job state model.
Only fixes the timeout and ignores idempotency.
Cannot describe compensation for duplicates already created.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

How would you design idempotency for email? For payments?
What happens if the worker crashes after the side effect?
How would you test retry safety?

Continue the section

Next in Azure Production Incident Debugging Essentials: Transient vs Query Regression

Step 13 of 15

Distinguish Azure SQL transient faults from query regressions

Practice route

Read core answer Review checklist Follow-up prompts Track progress

Finished this drill?

Practice freely. Sign in only when you want to save completion, confidence, notes, or bookmarks.

New to Aporeon? Create account

Drill details

Share the question with a concise Core-answer excerpt and invite other developers to add their perspective.

Was this drill useful?

Help improve the interview library.

Found this answer useful?

Say thanks with a standalone, one-time $5 contribution. No account required.

No subscription or perks.Choose another amount

Human editorial direction

Aporeon is shaped by Aleksandar Tomovski, a software developer with experience on both sides of technical interviews. Content is reviewed for accuracy, natural spoken delivery, useful depth, and honest trade-offs.

About the creator Editorial standards

Opening drill

A Service Bus worker produced the same external side effect twice. The second attempt has the same MessageId, DeliveryCount 2, and a lock-renewal failure after the provider call succeeded. How would you diagnose, contain, and repair it?

Debug duplicate Azure queue processing after lock loss

Diagnoses duplicate processing from Azure Service Bus lock loss or Storage Queue visibility behavior without repeating generic idempotency theory.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

A Service Bus worker produced the same external side effect twice. The second attempt has the same MessageId, DeliveryCount 2, and a lock-renewal failure after the provider call succeeded. How would you diagnose, contain, and repair it?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section

A Service Bus worker produced the same external side effect twice. The second attempt has the same MessageId, DeliveryCount 2, and a lock-renewal failure after the provider call succeeded. How would you diagnose, contain, and repair it?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section