Select to view content in your preferred language

ArcGIS for Power Automate Connectors are down!

1771
20
Jump to solution
06-09-2025 01:13 PM
AkshayHarshe
Esri Regular Contributor

Hello Everyone, 

Since this morning we are experiencing issues with our ArcGIS for Power Automate backend container which is causing connections to timeout and unable to load the feature layers in the organization throwing `The Dynamic invocation request failed error`. We are currently investigating the the cause and trying to get it fixed as soon as possible. We apologize for inconvenience and disruption.

Thanks,
Akshay Harshe
20 Replies
abureaux
MVP Frequent Contributor

The S123 Website was not properly responding this morning. It was about a 50-50 chance of flows (in my case at least) running. The issue was the server wasn't responding. Here are some screen caps (this is from an older flow, so the entire Create Report process is manual).

Checking the Feature Report template:

abureaux_0-1749676147265.png

Creating the Feature Report. Here is where you see the first real issue. The Create Report step ran the full 60 attempts (shouldn't take more than 1-2) before timing out. The end result was "esriJobSubmitted" which resulted in the flow failing as no Feature Report was generated:

abureaux_1-1749676213627.png

The issue was experienced both by my automations and manually running Feature Reports (see below). While the system time isn't captured here, those two running reports had been running for ~10 minutes. For context, see the successful runs of ~25 seconds. Again, the server was timing out randomly.

abureaux_2-1749676349187.png

 

0 Kudos
AkshayHarshe
Esri Regular Contributor

@abureaux are you using ArcGIS connectors in your flow? If not, the we have no control over the webhooks or processes they have created.  If this is still an issue with S123 webhook or create report, I would ask you to reach out to the S123 questions or support.

Thanks,
Akshay Harshe
0 Kudos
abureaux
MVP Frequent Contributor

Hi @AkshayHarshe. Yes this was related to the ArcGIS connectors; however, this was an old issue and has since been resolved.

The issue I was referring to here was that the servers on your end were getting overloaded which was causing a global issue. After some resource allocation on your end, this issue has since disappeared.

Unrelated to this post, I do still have two other issues which are also related directly to the ArcGIS connectors. But I have yet to bring this up with anyone though. The issues I am referring to are:

  1. The ArcGIS connectors will sometimes randomly stop working and send a fail response. However, my flows run regularly and will auto-correct these intermittent issues. This is a minor issue right now because it is such a transient issue. 
  2. The ArcGIS connectors regularly do not display layers. This is far more annoying, but I have found that adding layers to my Favourites is a decent workaround. Would be nice if related tables only showed up after selecting the main record as it would vastly reduce the size of this list, which is likely the issue. 
0 Kudos
AkshayHarshe
Esri Regular Contributor

@abureaux Yes, believe it or not there were 3 recent instances of outages. Once when our servers were throttled, once when ArcGIS Online had an outage and now when Azure services were affected. We apologies for the inconvenience.

Regarding your issues, Maybe a good idea to create a new threads for it so I can reference them in our roadmap and issues, but, I will acknowledge following about them 

1. I have seen this happen with webhooks and `Fetch updates, changes... ` action time to time and we are looking into it. Since it is so transient and dependent on ArcGIS Webhooks it is almost impossible to reproduce and troubleshoot. That said, we are working on it. If you are referring to something else, I would like to hear more about it. 

2. Ah yes! This unfortunately, completely out of our control. If you have lot of layers, the Power Automate dropdown sometimes takes a really long time to load and it is annoying as heck. But, this is completely Power Automate and even we have complained to them about this. You are doing the best workaround possible. Alternatively, you can copy the layer URL to `/0` and paste it as a custom value in the dropdown and it should pick it up.

Hope that helps.

Thanks,
Akshay Harshe
0 Kudos
abureaux
MVP Frequent Contributor

Thanks for the updates! Fantastic to hear on both counts.

I won't both making a new thread unless something changes. As you mentioned, the first is very transient which makes it both hard to test and also a minor issue to circumvent, and 2) unless something changes here, I'm content with the current functionality of the drop down.

Honestly, beyond those two minor issues, I'm loving the new connectors so far. Literally have hundreds of flows using them.

0 Kudos
AaronPDXPaul
Frequent Contributor

ArcGIS Connectors no longer work for us.

None of the ArcGIS Connectors are able to Trigger a Flow.

Can you please assist?

We are using a government version and ArcGIS Online

Thank you

0 Kudos
CalvinHarmin
Frequent Contributor

You might want to make your own thread for that, but the first thing to try is to go the ArcGIS Connection reference and perform the 'Switch account' step to log in again and re-authenticate. NOTE: if your browser session already has an active AGOL login session, this may automatically use that account instead of prompting you to enter credentials. If that's an issue, just navigate to any normal AGOL page and log out first. This authentication session expires within two weeks, if I am not mistaken. It's a big pain that has been discussed in other threads as well. 

CalvinHarmin_1-1761156597932.png

If that's not it, you may want to start your own thread so others can help you with your particular issue. 

0 Kudos
abureaux
MVP Frequent Contributor

haha. Now there is some quality advice! 😉

0 Kudos
abureaux
MVP Frequent Contributor

@AaronPDXPaul, I don't believe the connectors are down right now (I just got several outputs). Also, this specific thread's issue has been resolved.

Did you try refreshing your connection's credentials? This needs to be done regularly (every 2 weeks). To do this, go to Power Automate > Connections > locate the ArcGIS connection > click the ellipses (...) > Switch Account > log in using the appropriate credentials for that connector > click "Allow access" when prompted.

 abureaux_0-1761156693800.png

 

0 Kudos
AaronPDXPaul
Frequent Contributor

I believe connectors are down for government agencies.

Not for commercial private companies.

I deleted all connections.

Added new ones.

Reconnected.

Created 20-30 new Flows, tested with many REST services, tried everything possible.

Still nothing Triggers from REST Services on AGOL.

Our Org has nothing preventing flows from Triggering.

These Flows used to work for years.

Thoughts?

0 Kudos