Messenger error 2018395: Cannot join failed call
Last verified against Meta for Developers - Messenger Platform error codes
You cannot join a call that has failedWhat error 2018395 means
Code 2018395 means the call you tried to accept or join had already failed on Meta's side: "You cannot join a call that has failed." Meta's suggested solution is short: "Wait for the user to call back."
A failed call is different from an ended one. Ended (2018396) means the call was over: the person hung up or it was never answered. Failed means it broke during setup, so the call ID now refers to something that can never be connected. Retrying with the same call_id can only return the same error, and the person on the other side has typically already seen the call drop.
Because the platform owns the call state, your best tool is the calling webhooks. Subscribing to the calls field and tracking each call's lifecycle tells you when a call has failed before you attempt to act on it. If failures cluster, look at your own media path: an accept with bad connection data, as in 2018392, can be what pushes a call into a failed state in the first place.
What it looks like
{
"error": {
"message": "(#2018395) You cannot join a call that has failed",
"type": "OAuthException",
"code": 2018395,
"fbtrace_id": "BLBz/WZt8dN"
}
}Why it happens
- Accepting after the call already failed during setup.
- Retrying an accept after an earlier accept attempt with bad connection data.
- Network or media negotiation failures on either side.
- Late processing of queued connect webhooks.
How to fix Messenger error 2018395
- 1Stop acting on that call_id and mark the call failed in your system.
- 2Let your team or the person know the call did not connect; a short text message in the thread can invite them to call again.
- 3Check logs for an earlier accept error on the same call.
- 4Process connect webhooks immediately rather than from a slow queue.
How to stop it recurring
Track call state from webhooks, and check it before every action on a call. Get accept requests right on the first try with a validated payload, and alert on failure rates per Page so media problems surface early. A follow-up message after a failed call only works within the standard messaging window; see the Messenger limits reference.
Official reference: Meta for Developers - Messenger Platform error codes. See all Messenger error codes or the Messenger limits and quotas.
Related codes
Error 2018395 - quick answers
What does Messenger error 2018395 mean?
Code 2018395 means the call you tried to accept or join had already failed on Meta's side: "You cannot join a call that has failed." Meta's suggested solution is short: "Wait for the user to call back." A failed call is different from an ended one. Ended ( 2018396 ) means the call was over: the person hung up or it was never answered.
How do I fix Messenger error 2018395?
1. Stop acting on that call_id and mark the call failed in your system. 2. Let your team or the person know the call did not connect; a short text message in the thread can invite them to call again. 3. Check logs for an earlier accept error on the same call. 4. Process connect webhooks immediately rather than from a slow queue.
Should I retry after error 2018395?
No. Retrying the same request produces the same error; the condition has to be fixed first. Treat it as a permanent failure for that message and surface it, rather than looping.
Stop debugging Messenger by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.