Hi, I have a make.com automation where I created a dynamic squad for outbound calls, but the calls arent going through. I connected the number to the squad but the logs still say no assistant connected. Call ID: 7a9c9b8c-f751-4fc0-93ac-9c3cb2596da2

@Matilda I'm sorry to hear that you're experiencing issues with your outbound calls. To assist you better, I'll need a bit more information about how you've set up your squad. Could you please provide me with the following details? 1. How have you defined the members of your squad in the automation? 2. Have you ensured that the first member of the squad is set as the assistant that should start the call? 3. Are the assistants you've added to the squad marked as persistent or transient? Once I have this information, I'll be able to help you troubleshoot the issue more effectively.

the issue only came up after i switched the phone number.

@Matilda Thank you for providing additional context. If the issue started after you switched the phone number, it's possible that the new number may not be properly configured or associated with the squad. To help resolve this, please ensure the following: 1. The new phone number is correctly registered and verified on your platform. 2. The phone number is correctly linked to the squad in your automation. 3. The JSON payload for the automation is correctly formatted and includes the new phone number's unique identifier. If you've already checked these and the problem persists, it might be helpful to review the logs for any specific error messages related to the phone number change. If you can share the error message or any additional details from the logs, I can provide more targeted assistance. If you need further help with this issue, please don't hesitate to let me know.

The logs say no assistant connected but i already linked the new number to the squad

@Matilda It sounds like there might be an issue with the assistant's connection to the squad, despite the new number being linked. Here are a few steps you can take to troubleshoot this problem: 1. Double-check the assistant ID: Ensure that the assistant ID linked to the squad is correct and that the assistant is active and available. 2. Verify the squad configuration: Make sure that the squad is properly configured to include the assistant and that there are no restrictions preventing the assistant from connecting. 3. Check for any recent changes: Since the issue arose after changing the phone number, review any other recent changes to the automation that could affect the assistant's connection. 4. Review assistant permissions: Confirm that the assistant has the necessary permissions to make outbound calls and that there are no limitations on the account that could be causing the issue. 5. Test with the previous number: If possible, try reverting to the previous phone number temporarily to see if the issue is specifically related to the new number. If you've gone through these steps and the issue persists, it may be necessary to look deeper into the system logs or configuration. Since the logs indicate "no assistant connected," it could be a sign of an assistant-not-found or assistant-not-invalid issue as per the context provided. If you're unable to resolve the issue with these suggestions, please let me know, and we can explore further steps or escalate this to the appropriate support team for more in-depth assistance.

logs

🔵 07:13:46:916 Call

7a9c9b8c-f751-4fc0-93ac-9c3cb2596da2

Waited 300s But Transport Never Connected. @Matilda the call was never connected because of this you observed call failure it's coming from telephony side notthing wrong on your side.

still getting a 201 without the actual call (0c77a181-ef9c-44d5-85c4-17b489ae46e7) sometimes it says over concurrency limit

@Matilda can you try again I have reset your concurrency limit.