Mar 16 , 11:41 PDT
Investigating - Starting ~15:33 UTC (10:33 AM PT), batch calls were not being sent due to an internal issue that was triggered in our system. We’ve identified the root cause and are actively working on a fix.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Scheduled batch calls not running | 0 | 13 | February 2, 2026 | |
| Batch outbound calls not sending | 0 | 10 | February 20, 2026 | |
| Outbound Batch Calls Showing "Sent" Status But Zero Calls Actually Placed | 2 | 20 | March 11, 2026 | |
| Calls failing to start and concurrency stuck | 0 | 10 | February 19, 2026 | |
| Inconsistent response code for /create-batch-call | 4 | 7 | March 13, 2026 |