To prevent "Over Concurrency Limit" errors, implement a call queue using Twilio to hold excess calls and process them as capacity becomes available. Here’s a code snippet for a manual queue processing endpoint you can add to your server:

js
app.post('/process-queue', async (req, res) => {
  try {
    await processQueue();
    const activeCalls = await getActiveCalls();
    const callsInQueue = await getCallsInQueue();
    res.json({ message: 'Queue processing triggered', activeCalls, callsInQueue, maxConcurrency: MAX_CONCURRENCY });
  } catch (error) {
    res.status(500).json({ error: 'Failed to process queue' });
  }
});

This approach ensures calls are queued and only processed when your concurrency slots are available, reducing failed calls due to rate limits. For full implementation details, see the [Vapi call queue management guide](https://docs.vapi.ai/calls/call-queue-management). Source: - [Call queue management with Twilio](https://docs.vapi.ai/calls/call-queue-management)

thanks. i have a q and distributing 15 calls per min. and the average call is less than 20 sec. how come i am still hitting the concurrency limit?

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.

bf69a11b-c78e-4a97-a8d6-5599c6548eb1

i am getting an issue related to incoming call on my number on vapi , """call.start.error-get-assistant""" Can you please tell me the reason why this is happening

Hi, thanks for sharing your details. Our team will look into it and get back to you soon with an update.