I made some batch calls which worked up until a couple of the numbers started having a loading circle for hours, nothing changing. I canceled the batch but still didnt change anything. main problem being it says i cant do outbound or inbound with it because it hit the concurrency limit, but theres no active calls?!?!? Checked everything, the log, the batch and still nothing. Please help. https://cdn.discordapp.com/attachments/1425773084002222100/1425773084358742026/image.png?ex=68e8ce28&is=68e77ca8&hm=7628f62275a4fe5bc2853191c661391d432a6a3bb8208a006734e080aa43eb6f&

Quick Fix: When the concurrency limit is reached but no active calls are shown, the most effective step is to restart your server to reset the concurrency counter. This often clears stuck states caused by missed webhooks or internal errors.

bash
# Example: Restart your Node.js server
pm2 restart all
# or, if running directly
Ctrl+C and then: node server.js

If the issue persists after a restart, check your webhook URLs and server logs for errors as described in the [Vapi troubleshooting guide](https://docs.vapi.ai/calls/call-queue-management). Source: - [Call queue management with Twilio](https://docs.vapi.ai/calls/call-queue-management)

This is not helpful, please! i need help fast (i dont have a node server and havent done all those things, i just used outbound on vapi)

Hey, can you share the org_id? You can find it [here](https://dashboard.vapi.ai/org/settings). This will help me get more details about it.

812bc175-1d4d-4a1f-b974-c4a43a6ba7f0 , this is the org id

Is it working now?

nope, when i call the number it still says concurrency limit is reached

Okay try now

its good now, have any idea when you will fix this forever?

We are working on it.