enable duplicate detection on an azure service bus queue that also uses scheduled messages
domain: learn.microsoft.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Enable duplicate detection when creating the queue or topic, since it cannot be turned on after creation.
Set the duplicate detection history time window to a value between 20 seconds and 7 days, with a default of 10 minutes, balancing dedup coverage against throughput overhead.
Confirm scheduled messages participate in duplicate detection the same as regular messages, with the window starting at the time the message is enqueued.
Set a client-side message id consistently for logically identical messages so the service can recognize resends within the window.
Keep the duplicate detection window as small as your retry semantics allow, since every message id must be checked against the retained window on each send.
Known gotchas
Duplicate detection must be enabled at entity creation time; you cannot retrofit it onto an existing queue or topic without recreating it.
If a non-scheduled message and a duplicate scheduled message share a message id, the scheduled one is silently dropped, which can be surprising if you expected the schedule to still fire.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?