REST API Tool Error

(1) Share

Report

Posted on by ML-02022038-0

When trying to add a rest api tool to my agent, I get this error when uploading my spec file:

There is already a connector enabled for this REST API. If you would like to proceed anyway, please update the Tool name. But there is no connector.

I have deleted all solutions, agents, connectors etc. from my account so it is essentially a fresh account. Then I try again with a new spec file with a new name and a new URL and I still get this error. There is something I cannot see that is cached or saved that i cannot delete that is preventing me from adding a new rest API.

Categories:

Copilot Studio pre-built agents/templates

I have the same question (0)

All responses (2)

Answers (0)

Sort by

MichaelFP 1,999 Moderator on at

Like (2)

Report
Copy link

Link copied!

Do you have more developers working on the same environment? Can you share some screenshots?

If more information we can help

Was this reply helpful? Yes No
Suggested answer

Valantis 5,303 on at

Like (1)

Report
Copy link

Link copied!

Hi @ML-02022038-0,

The problem is that deleting solutions and agents doesn't delete the custom connectors that the REST API tool wizard created in the background. Those connectors live at the environment level and aren't removed when you delete solutions.

The system is detecting a connector pointing to the same API host URL and throwing that error even though you can't see it through the normal UI.

To find and delete the hidden connectors:

1. Go to make.powerapps.com
2. Make sure you're in the correct environment (top right)
3. Go to Data > Custom Connectors in the left nav
4. You should see connectors there that weren't visible when you deleted your solutions
5. Delete all of them

Alternatively, if you don't see them in Power Apps, check in Power Platform Admin Center > your environment > Resources > Connectors.

After deleting those connectors, try adding the REST API tool again. If the error still appears with a completely different host URL in your spec, it may be an environment-level caching issue and the fix is to try in a different environment.

Also double-check that your spec file uses a unique host URL the error triggers on host URL match, not just on connector name. If your new spec still points to the same server URL as a previous attempt, the system will block it.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No