Answered

Custom connector - already successful flow failed - connector testing successful, flow running failed

(0) Share

Report

Posted on by Community Power Pla...

Hi,

since a few days, my flow, using a custom connection, failed at my action --> "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."

The flow itself as well as on the API side, no changes were made since the last successful run (last week).

If I'm testing the connection at the connector settings, it is successful, I got the expected response.

If I'm testing my API with Postman, it is successful.

If I run the flow, it failed.

I setup a new connector as well as a new flow using this new connection, but still get the same failure.

I tried to setup a new connector manually as well as by importing the Postman Collection, same behavior.

Any idea what's going on here?

Categories:

Using connectors

I have the same question (0)

All responses (3)

Answers (1)

psycrkz1 on at

Like (0)

Report

There are three things you can check accordingly:

1. Save this existing flow with a new copy and try to run the flow with the custom connector to see if would help

2. Try to use HTTP action instead of using custom connector to call the REST Web API directly similar as Postman to see if this is a possible workaround

3. Did you have any parameters pass to this custom connector or not? Make sure the header and body of this custom action is the same as test in your Postman

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

thanks for your hints.
I tried both, resulting in the same failure. The action in the flow fails.

I don't understand why I got this error now, the flow was already running successful the last weeks. And the test within the settings of the custom connector is successful.
Are there some changes in the backend of power automate since last week? I didn't change anything within my flow or my API.

Was this reply helpful? Yes No
Verified answer

Community Power Pla... on at

Like (0)

Report

Another test was successful.
I used the action HTTP to request my API. I defined all parameters directly within the url and it work.
I have my workaround.

Was this reply helpful? Yes No