Failed TO Fetch Agents

[luca.godano]

Hello,

I’m facing an issue with the main workspace of my retell ai account. I created many vocal agents but when I go to the page Phone Numbers I get the message “Failed to Fetch Agents” and I am not able to associate my agent for inbound calls.

Could you please take a look at it.

email: luca.godano@gmail.com

workspace name: SmartService

[shaw]

Hey @luca.godano Can you share your workspace ID ? and screenshot of error.

[luca.godano]

Hi Shaw, thanks for your reply. I opened a support ticket also on retell and they told me that it is a backend issue with my workspace that they need to fix and that they would let me know once fixed.

I am quite annoyed because just today I planned to put on production some changes I made to one agent for a client but I am not able to do that.

I have got other workspaces and this problem is not happening.

I am not able to see the workspaceId but the name of the workspace is SmartService and from the dev tools I was able to get the organizationId that is org_1EtJTSOlVx0Iqpu4

[shaw]

Hey @luca.godano Ok i check with the team.

[shaw]

Hello @luca.godano

The agent-list call that powers the Phone Numbers dropdown is failing on a stale internal record, which is why the page shows “Failed to Fetch Agents”. Your agents themselves are intact — only the listing call is affected, so other dashboard areas that don’t enumerate all agents continue to work.

While we investigate and clean up the stale record on our side, you can bind an inbound agent directly via API instead of the dashboard:

• Endpoint: PATCH https://api.retellai.com/update-phone-number/{your_phone_number}
• Body (current schema):
  ```json
  { “inbound_agents”: [ { “agent_id”: “<your_agent_id>”, “agent_version”: , “weight”: 1 } ] }
  ```
• Docs: https://docs.retellai.com/api-references/update-phone-number

One caveat: this is a workaround, not a fix. The API binding call validates the agent through the same internal lookup that’s currently failing, so please target a healthy agent (e.g. one you can see working in calls/playground). If you specifically want to bind agent_744e234ffe01a0b13412e7d0a8 and the API returns “Invalid inbound agent”, that’s expected — it’s the same stale record — and the cleanup needs to finish before that specific agent can be bound.

Thank You

[luca.godano]

Hi Shaw,

thanks for the update and for proposing a temporary solution. Your solution looks great!

I will use the API you have mentioned to bind the inbound agent.

Thanks again for your help and have a nice weekend!