River91218
02/24/2026, 2:01 PMoverride_agent_id. On Feb 23, a call was created with the correct agent ID — confirmed in the API response — but executed by the wrong agent.
Agents
- Outbound Opener: agent_e7ef2727e9d5ed6b8b9e4eb6ae
- Vida Colectivo: agent_61856b2f6f87d0d09fd12c12ff
Affected calls
- call_25b0d1e82d2cfbfaa5bb1f7cf4d → +542615175476
- call_28fd0af574bcdb62ba3e103d2e8 → +542612654027
Request sent
json
{"from_number":"+542614138019","to_number":"+542615175476","override_agent_id":"agent_e7ef2727e9d5ed6b8b9e4eb6ae","metadata":{"identificador":"2615175476"}}
API response confirmed
agent_id: agent_e7ef2727e9d5ed6b8b9e4eb6ae / agent_name: Mayorazgo: Outbound Opener
Actual behavior
Call was conducted by agent_61856b2f6f87d0d09fd12c12ff (Vida Colectivo).
Suspected cause
Both automations ran concurrently at 11hs using the same from_number with different override_agent_id values. We believe Retell may have misassigned the agent internally after registration. Our n8n workflows and payloads have been fully verified.
Could concurrent calls from the same from_number with different override_agent_id values cause agent misassignment?Shah - support @ Retell AI
02/24/2026, 2:16 PMShah - support @ Retell AI
02/24/2026, 2:17 PMRiver91218
02/24/2026, 6:50 PMRiver91218
02/25/2026, 6:38 PMRiver91218
02/27/2026, 1:44 PMShah - support @ Retell AI
02/27/2026, 2:00 PMShah - support @ Retell AI
02/27/2026, 2:01 PMRiver91218
02/27/2026, 2:04 PMShehroze -Support @Retell
02/27/2026, 8:52 PMRiver91218
03/02/2026, 3:45 PM