{"version":"2.1.277","anchor":"duplicate-submit-guard-added-to-fleet-dispatch-and-fleet-rep","canonical_anchor":"duplicate-submit-guard-added-to-fleet-dispatch-and-fleet-rep","heading":"Duplicate-submit guard added to fleet dispatch and fleet reply ( sameChunk )","tier":"internal","area":"Fleet","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/duplicate-submit-guard-added-to-fleet-dispatch-and-fleet-rep","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Duplicate-submit guard added to fleet dispatch and fleet reply (`sameChunk`)\n\nFleet dispatch and fleet reply now guard against accidentally sending the same command or reply twice\n\n**What**\n\nFleet's command dispatcher and reply composer now record a short-lived timestamp per query to detect duplicate sends. If a duplicate fire happens within the same event cycle or a short time window, it's silently dropped instead of being processed a second time.\n\n**Why**\n\nThis prevents a command or reply in FleetView from being submitted twice due to rapid duplicate triggers, such as double clicks or overlapping event handlers.\n\n- Area: Fleet\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}