https://retellai.com/?utm_source=discord&utm_medium=seo logo
Hi evy pelase check we initated the batch call tho...
# ❓・ai-evy-support
r
@AI Evy Hi evy pelase check we initated the batch call thorugh API and out 10, 8 of them were successfull and the rest (2) stucked somewhere and in the call history we can not see them why? https://cdn.discordapp.com/attachments/1302816169367044149/1458438857203781726/image.png?ex=695fa488&is=695e5308&hm=389cfce681fbfd6f4f515cdea060f4929220416c1699900c0cf9fda70f8846db&
a
Thanks for tagging me @Rufi. I'll look through relevant sources and get back to you shortly.
### Answer Based on similar reports, there can be a UI delay where the batch call dashboard shows fewer "sent" calls than actually went through. [(1) ]() To verify your actual call status: 1. Check Call History directly — Click on "Call Logs" and check the total sessions at the bottom. The calls may have been sent even if the batch call display hasn't updated. 2. Use the List Calls API to retrieve all calls and verify their status programmatically. [(2) ]() Possible reasons calls don't appear: - If the calls failed to connect (e.g.,
dial_failed
,
dial_no_answer
,
dial_busy
) , they would still appear in call history with those disconnection reasons. - There may be a display/UI delay between when calls are sent and when they appear in the interface. [(1) ]() Recommended next steps: - Share your
batch_call_id
with Retell support so they can investigate the specific status of those 2 missing calls - Check if the destination numbers for those 2 calls were valid and reachable If the issue persists, I'd recommend reaching out via [Contact Sales]() for direct support with your batch call ID.
​ To learn more, see the sources I considered: [[1] Batch Calls Stuck at "Ongoing" Status](https://discord.com/channels/1186424376300679209/1450001150135894101) [[2] List Calls](https://docs.retellai.com/api-references/list-calls) ​
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
r
when i retreved ongoign calls it gave empty array but i see 2 in concurrency
a
Thanks for the follow-up, @Rufi. I'll get back to you soon.
### Answer --- This discrepancy (empty array from API but 2 showing in concurrency) suggests those calls may be in a transitional state that the API isn't returning as expected. Possible explanations: 1. Call status mismatch — The List Calls API filters by
call_status
which includes:
registered
,
not_connected
,
ongoing
,
ended
,
error
[(1) ]() 2. Calls stuck in
registered
state
— If the calls are showing in concurrency but not appearing as
ongoing
, they may be stuck in
registered
status (call ID issued, starting to make a call) rather than
ongoing
(call connected and ongoing) Try this filter to catch all active states:
Copy code
json
{
  "filter_criteria": {
    "call_status": ["registered", "ongoing"]
  }
}
Recommended next steps: - Try filtering for
registered
status in addition to
ongoing
- Share your
batch_call_id
with Retell support — they can investigate why those 2 calls are consuming concurrency but not appearing in the expected call status If the calls are genuinely stuck, this would require Retell support to investigate on the backend.
​ To learn more, see the sources I considered: [[1] List Calls](https://docs.retellai.com/api-references/list-calls) ​
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
r
I listed like that it gave empty array again @AI Evy
a
Thanks for the follow-up, @Rufi. I'll get back to you soon.
### Answer If the List Calls API returns an empty array even when filtering for
registered
and
ongoing
statuses, but you still see 2 calls in concurrency, this is a known issue where calls can become stuck in a state that doesn't properly reflect in the API. [(1) ]() What's happening: Based on similar reports, calls can sometimes get stuck where the status doesn't change properly — the call may have already ended but the status remains as "ongoing" in the concurrency count. Unfortunately, there is no API endpoint to force-end a stuck call. Users have reported trying to disconnect the agent from the number and even deleting/re-purchasing the number, but the stuck calls persisted. Recommended action: You'll need to contact Retell support directly with your specific
call_id
values (if you have them from the batch call response) or your
batch_call_id
. The Retell team can investigate and manually resolve stuck calls on the backend. In previous cases, Retell confirmed that stuck calls would not be charged. Check out these potentially useful sources: [List Calls]() , [Contact Sales]() Would you like me to provide a general answer on how to retrieve call IDs from your batch call initiation response?
​ To learn more, see the sources I considered: [[1] Infinitely ongoing call without any control to stop.](https://discord.com/channels/1186424376300679209/1278592880017014825) ​
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.