5-to-10-second wait so three rapid texts from the same customer bundle into a single run instead of launching three parallel replies.
dnd status, and live calendar slot rather than relying on the state captured when the run started.
Last Booking Appointment ID or Last Outbound Message ID) as soon as the action completes so any timeout retry checks that field first and skips duplicate sends.
Prevent concurrent agent runs, stale-state writes, and duplicate retry sends in sub-account <YOUR_LOCATION_ID>: 1. In Automation > Workflow > Settings, disable Allow re-entry on the active inbound message workflow and add an initial 8-second batching wait to bundle consecutive customer texts. 2. In Automation > Workflow Builder, add an If/Else check immediately before any calendar booking, opportunity update, or outbound message to verify current stage and slot availability. 3. In Settings > Custom Fields, record Last Booking Appointment ID and Last Outbound Message ID after each irreversible action and skip retries when already populated.
# Audit workflow re-entry settings, custom receipt fields, and execution logs ghl-crm custom-fields list --context <YOUR_CONTEXT> --location <YOUR_LOCATION_ID> ghl-crm workflows list --context <YOUR_CONTEXT> --location <YOUR_LOCATION_ID>
Official GHL MCP vs. ghl-tools: HighLevel’s official hosted MCP (services.leadconnectorhq.com/mcp) covers public v2 CRM records (contacts, opportunities, appointments, conversations). ghl-tools MCP complements it with workflow graph inspection & recipes, funnel/form builders, DNS/BIMI checks, and ghl-crm doctor audits.
| Step | Menu Path in GHL | Action |
|---|---|---|
| Step 1 | Automation > Workflow > Settings | Turn Allow re-entry off on your active agent handling workflow and start with a short 5-to-10-second wait so three rapid texts from the same customer bundle into a single run instead of launching three parallel replies. |
| Step 2 | Automation > Workflow Builder | Place an If/Else check immediately in front of your booking or stage-update action to re-verify the contact's current pipeline stage, dnd status, and live calendar slot rather than relying on the state captured when the run started. |
| Step 3 | Settings > Custom Fields | Save the confirmation artifact (Last Booking Appointment ID or Last Outbound Message ID) as soon as the action completes so any timeout retry checks that field first and skips duplicate sends. |
Connect Claude Code, Cursor, or OpenAI Codex to our ghl-tools MCP Server & Rust CLI to build workflows, forms, and funnels from your editor, or start your GoHighLevel plan through our partner link to unlock $612+ in ready-to-import kits (including GHL Production AI Agent Concurrency & State Guard Kit) and weekly live clinics.