https://retellai.com/?utm_source=discord&utm_medium=seo logo
our bulk calling stopped/paused, single outbound c...
# ❓・ai-evy-support
b
@AI Evy our bulk calling stopped/paused, single outbound call still works. Recent payment successful, what's wrong?
a
Thanks for tagging me @ben5276. I'll look through relevant sources and get back to you shortly.
### Answer Since single outbound calls work but batch calling stopped, here are a few things to check: 1. Batch Call Status Check your batch call status in the Batch Call tab. Batch calls can be in different states: Draft, Planned, Ongoing, or Sent. [(1) ]() 2. Time Window Configuration If you configured a Batch Call Window, calls will only go out during the specified hours and days. Verify your time window settings haven't restricted when calls can run. [(2) ]() 3. Concurrency Limits Batch calls queue without hitting concurrency limits, but if
concurrency_limit_reached
appears as a disconnection reason, you may need to add retry logic with exponential backoff or consider an enterprise plan. [(3) ]() 4. Check Call History Metrics In the batch call details, review the metrics (Sent, Picked Up, Successful) and click the history icon to view individual call details and disconnection reasons. [(1) ]() 5. Disconnection Reasons to Look For Common error disconnection reasons include: -
concurrency_limit_reached
– concurrency limit hit -
no_valid_payment
– payment issue (though you mentioned payment is successful) -
error_retell
– unspecified Retell-side problem [(3) ]() Could you check the batch call status and share any disconnection reasons you're seeing on the failed calls? That will help narrow down the issue.
​ To learn more, see the sources I considered: [[1] Create Batch calls](https://docs.retellai.com/deploy/make-batch-call) [[2] Platform Changelogs | Retell AI](https://www.retellai.com/changelog) [[3] Debug call disconnection](https://docs.retellai.com/reliability/debug-call-disconnect) ​
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
b
looks like the batch call stuck at ongoing
@AI Evy looks like the batch call stuck at ongoing
a
Thanks for the follow-up, @ben5276. I'll get back to you soon.
### Answer A batch call stuck in "Ongoing" status is a known issue that has been reported and resolved by the Retell team before. [(1) ]() [(2) ]() Recommended Steps: 1. Check Retell System Status – Visit the [Retell AI Status Page]() to see if there are any ongoing system issues affecting campaign processing. [(1) ]() 2. Verify Phone Number Setup – Ensure your phone number is active and linked correctly to your agent. 3. Review Campaign Settings – Double-check your schedule, time zone, and contact list configurations. 4. Contact Support with Your Batch IDs – If the issue persists, share your batch call IDs with the Retell support team so they can investigate. In previous cases, there was a task blocking others that required dev intervention to fix. [(1) ]() [(2) ]() Based on past reports, stuck batch calls have sometimes resolved on their own after some time, or required the Retell team to manually address a blocking task. [(2) ]() Could you share your batch call IDs here so support can take a look?
​ To learn more, see the sources I considered: [[1] Batch Call "Ongoing Status" for hours.](https://discord.com/channels/1186424376300679209/1346450553281970208) [[2] Batch Calling Stuck in Ongoing](https://discord.com/channels/1186424376300679209/1441826639653896222) ​
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.