Messenger error 2018396: Cannot join ended call
Last verified against Meta for Developers - Messenger Platform error codes
You cannot join a call that has endedWhat error 2018396 means
Code 2018396 means your app tried to accept a call that was already over: "You cannot join a call that has ended." As with failed calls, Meta's guidance is to "wait for the user to call back."
The accept-call guide supplies the usual reason. After the connect webhook arrives, your app has 60 seconds to accept; if it does not respond, the call terminates for the person. A call can also end because the person hung up while it was ringing. In both cases the call ID is now history, and an accept request carrying it gets 2018396.
That makes this error mostly a latency signal. If it happens occasionally, people are hanging up before your agents pick up, which is normal. If it happens often, measure the gap between webhook receipt and your accept request: slow webhook processing, queueing behind other events, cold-starting servers, or agents taking too long to click answer will all eat the window. The related 2018395 covers calls that failed rather than ended, and 2018390 covers IDs the platform does not recognize at all.
What it looks like
{
"error": {
"message": "(#2018396) You cannot join a call that has ended",
"type": "OAuthException",
"code": 2018396,
"fbtrace_id": "BLBz/WZt8dN"
}
}Why it happens
- Accepting more than 60 seconds after the connect webhook.
- The person hanging up before the call was answered.
- Webhook processing delays: queues, retries or cold starts.
- Agent tooling that waits for a human to click answer without showing elapsed time.
How to fix Messenger error 2018396
- 1Mark the call as missed and stop retrying the accept.
- 2Measure time from webhook receipt to accept request for recent calls.
- 3Process calls events on a fast path separate from message webhooks.
- 4Show agents a ringing countdown so they answer inside the window.
- 5Send a follow-up message in the thread to invite a call back while the window is open.
How to stop it recurring
Size your answering capacity to the 60-second window: route calls only to agents who are available, keep calling webhooks off any shared slow queue, and report missed-call counts per hour. Webhook latency is often the hidden cost; the webhook debugging guide shows how to measure delivery delays.
Official reference: Meta for Developers - Messenger Platform error codes. See all Messenger error codes or the Messenger limits and quotas.
Related codes
Error 2018396 - quick answers
What does Messenger error 2018396 mean?
Code 2018396 means your app tried to accept a call that was already over: "You cannot join a call that has ended." As with failed calls, Meta's guidance is to "wait for the user to call back." The accept-call guide supplies the usual reason. After the connect webhook arrives, your app has 60 seconds to accept; if it does not respond, the call terminates for the person.
How do I fix Messenger error 2018396?
1. Mark the call as missed and stop retrying the accept. 2. Measure time from webhook receipt to accept request for recent calls. 3. Process calls events on a fast path separate from message webhooks. 4. Show agents a ringing countdown so they answer inside the window. 5. Send a follow-up message in the thread to invite a call back while the window is open.
Should I retry after error 2018396?
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.