[Troubleshooting](https://missblue.dev/help/collections/troubleshooting) # Prevent duplicate messages from retries and automations Trace repeated sends and make a retry decision without messaging the customer twice. Miss Blue team Updated September 14, 2026 2 min read [Browse this collection](https://missblue.dev/help/collections/troubleshooting) ## Pause the repeated action and inspect history If a customer receives repeated copies, pause the relevant external workflow while you inspect the sends. Compare the sending number, message IDs, timestamps, and workflow execution records. Look for overlapping automations, repeated enrollment, a teammate replying alongside an automation, or a retry after a timeout. Similar text alone does not show whether two distinct sends occurred; compare the recorded IDs. ## Deduplicate before creating a send The public send API does not currently accept a client-supplied idempotency key. Your integration should durably record the workflow execution or business action before sending and save the returned Miss Blue message ID. A webhook delivery can be retried. Process each event envelope ID once, and update existing message mappings when new information arrives for the same message. Do not turn your own outbound synchronization events into a fresh customer reply. ## Reconcile an uncertain result 1. If a send times out or reports Outcome unknown, inspect the message record and the conversation first. 2. If a file and text were sent together, check each resulting message separately. 3. Only retry after you can distinguish a confirmed failure from an attempt that may already have reached the sending system. 4. If the outcome stays uncertain, give support the request and message details before sending another copy. **Keep in mind** allow\_duplicate is an explicit override for intentional repeated content, not a retry or idempotency mechanism. ## Check GoHighLevel confirmation states The connected inbox deduplicates repeated deliveries of the same GHL message ID. Different workflow executions can still represent separate sends. Confirmation missing requires checking the actual GHL conversation; the integration deliberately avoids blindly posting another copy. - [API send and retry details](https://missblue.dev/docs/sending-messages) ## Related articles - [Set up webhooks for replies and delivery events Choose events, store the signing secret, and diagnose a receiver that is not accepting deliveries. 3 min read](https://missblue.dev/help/articles/set-up-webhooks) - [Connect GoHighLevel with Beta access Request Beta access, connect a sub-account, and verify direct messages and media in both inboxes. 2 min read](https://missblue.dev/help/articles/connect-gohighlevel) - [Troubleshoot pending or failed messages Work out whether a send was rejected, is still awaiting confirmation, or needs help from support. 3 min read](https://missblue.dev/help/articles/troubleshoot-message-delivery) ## Still need a hand? Send us your question, or text the team at (929) 272-7048. [Contact the team](https://missblue.dev/contact) [Text us](sms:+19292727048)