Can't add custom connector action within agent tools

(0) Share

Report

Posted on by ksoze92

103

Hello there,

I have a custom connector that is working perfectly fine in power automate, power apps.

On top of that, I have already added couple of actions within my copilot agent's toolset (and they work well).

However yesterday I updated my custom connector (added more actions and some custom code), tested it (worked fine) and afterwards I tried to add one of the newly created actions into my copilot agent toolset.

It seems that the tool (i.e. custom connector action) is added but an error prompts all the time (I thought it was transient but today still happens).

The error says:

ErrorThis Tool has encountered an error obtaining required dependencies. Please re-create the component or restore from a backup to resolve the problem.

Can anybody help? This is really annoying

Thank you!

Andoni

Categories:

Calling actions from Copilot Studio

I have the same question (6)

All responses (5)

Answers (0)

Sort by

stampcoin 5,153 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

@ksoze92 Hi,

Please try to delete it, publish the agent and then re-add your custom connector.

Was this reply helpful? Yes No
Michael E. Gernaey 53,978 Moderator on at

Like (1)

Report
Copy link

Link copied!

Hi @ksoze92

Just to verify also. Everything is republished fine prior to updating the bot? I know you said tested, but tested as in from PA itself?

Normally when a custom connector doesn't work its due to metadata in the agent. Ahhh I actually see @stampcoin post now so yeah do what he said and if not, close the Agent, republish your connector, test it and then go back into the bot.

I would be curious also, if the above/below do not work, if you create a second Agent does it work there? That will help pinpoint if its directly the metadata or the Agent.

Was this reply helpful? Yes No
ksoze92 103 on at

Like (0)

Report
Copy link

Link copied!

Hi guys,

I waited some days (I tried this on Friday afternoon, retried on Saturday morning and waited till now - Monday morning -) and it is working. I deleted the tool when it was not working, waited the period mentioned above, retried today and it works. However I have this same problem with other recently added tools too (i.e. whenever I edit my custom connector and try to add the new actions to the copilot agent this problem happens).

Next time I will try what you guys proposed to see if I can speed things up. Thank you!

Was this reply helpful? Yes No
chiaraalina 1,929 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
It seems sometimes Copilot Studio can no longer load new operations from an existing custom connector.

Existing operations still work, but any new or renamed operation ID fails with the error: “This Tool has encountered an error obtaining required dependencies.”

My observation:

The same operation works in the Custom Connector Test and in Power Automate. No problems there. It fails ONLY when added as a Tool in Copilot Studio.

Renaming the operation ID causes the Tool to break immediately. Meaning I get the same error for working tools if I change operation ID in the definitions in the custom connector.

Changing the ID back to the old value makes it work again.

Solution that worked for me:

--> Creating a NEW connector with the same Swagger works perfectly: New operation IDs load correctly as Tools.

This is by now the only solution that helped me. Copying the swagger from the swagger editor and creating a new custom connector.

Hope it helps someone else too!

2 people found this reply helpful.

Was this reply helpful? Yes No
Hector L. 2 on at

Like (0)

Report
Copy link

Link copied!

This is very annoying. I got the first action working, added the tool in studio, then added the 2nd action. It generated that error. It seems that once you create the action, then let studio consume it, subsequent actions added to the connector fail to load. Only way I seem to work around this is to delete the agent completely, then recreate it with all the actions already created. Something is happening after the 1st load that subsequent loads cannot process (it sees something its not expecting to see or it doesnt see something it expects to see).

Was this reply helpful? Yes No