nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Connectors broke in government version - Do ArcGIS Connectors work for anyone?

AaronPDXPaul

Do ArcGIS Connectors work for anyone using the government version?

Using ArcGIS Online REST Services.

I believe ArcGIS Connectors are broke for all government agencies.

Ours used to work.

Now, the simplest of Flows won't even Trigger.

Delete

Create

Update

None of these work, no error, just nothing.

Esri tech support can't help and are stuck.

If anyone just says there's is working, I guess we will look internally at what's "wrong"

Thank you

Create FS.jpg

Find more posts tagged with

Accepted answers

Akshay Harshe

This is Spot on, I really appreciate you going extra mile to test these things. yes, S123 webhook is sent from the client and others are created on the server/AGOL. I just came back from time off and tested this on ArcGIS Online today through Power Automate and using Webhook.site and the webhooks are not triggering for me either. I have reached out to the ArcGIS Online team and there has been an issue with webhooks in the recent release of ArcGIS Online and they are working on a patch.

All comments

Akshay Harshe

@AaronPDXPaul Can you please confirm if you can create a flow with a manual trigger and use Get data from feature layer action? If it works I doubt it is related to the outage.

Also, Does flow checker has any errors? Navigate to the Flow page and open the flow checker.

Here is the guide to troubleshoot the webhooks: Guide: Troubleshooting ArcGIS and ArcGIS Enterpris... - Esri Community

AaronPDXPaul

We've gone extensively through the trouble shooting guide with Esri Support.

All is set correctly.

We do have one error message.

We have more than 20 different ways and time, on different Flows and Services, deleted all connections, added them back, then reassociated to the Flow and/or recreated the Flow entirely.

We can't get a REST to Trigger a Flow.

So, no Actions below it matter until the Flow is Triggered.

We appreciate your insights.

As we can't see deep enough into the issue

CalvinHarmin

We are on government Power Automate. I did a test just now by creating a new hosted feature layer (HFL). I created a flow like in your example to trigger based on new record creation. I had to go into the HFL and manually enable "Keep track of changes to the data (add, update, delete features)" in order for the webhook from the flow to be created.

Creation of new records did not trigger the automated flow.

I turned the flow 'off' which removed the webhook, turned it back on to create a new webhook... but it still does not trigger.

I made different manually triggered test flow using ArcGIS connector ("Get data from feature layer") and that does work.

Akshay Harshe

@AaronPDXPaul I understand your frustration and I want to help you get this resolved. Unfortunately, I don't have a access to the government cloud but I will get someone to test the webhooks. Apologies for the inconvenience. I assure that our backend is up and running at this point.

@CalvinHarmin Thanks for testing and confirming that webhooks/triggers are not working for you and returning response but Get data from FL is working.

All triggers in ArcGIS connectors except for `When survey response is submitted` are directly dependent on ArcGIS REST API. Power automate triggers wait on the webhook to tell it that changes are there, and the Fetch updates changes action will call `extractChanges` endpoint to retrieve the changes. So it might not be an issue with the ArcGIS Connectors that we can fix. I would appreciate as much information as possible to get you the right help.

I have a few questions: Were your flows working before? and was it after Azure outage they stopped working?

Has anything regarding your security changed recently? While I do not know how this works in GCC. I have seen webhooks not triggering when certain ports weren't open when using Enterprise connectors or some URLs were blocked by firewalls or referrer urls were not listed for Power Automate in Online.

If you haven't tried like @CalvinHarmin, create a flow with a manual trigger and run get data from feature layer action. If this works we know at least there is something working! This also confirms that that the connection between ArcGIS and Power Automate in your GCC works.

Lets take it from there.

Akshay Harshe

One other thing you can try is to create a webhook directly using HTTP Webhook trigger available in OOTB in Power Automate. See if they work when you completely bypass all the triggers in ArcGIS Connector.

If they still don't work then it is not related to ArcGIS connector and probably an issue with ArcGIS Online. If they work with this and not with ArcGIS triggers then we need to investigate this further.

You can take this completely out of Power Automate and test webhooks using something like webhook.site.

We normally don't see any disparity in GCC vs Powe Automate online. but in either case we would like to know.

AaronPDXPaul

Thank you for verifying.

ArcGIS Connectors are broke for other government agencies like ours.

Do you know if esri plans to fix or wait months for an update?

It seems odd they'd just leave it broke.

Thanks,
Aaron

AaronPDXPaul

@CalvinHarmin is having the same issue, and I see in other forums others are too.

Can anyone from esri help me?

I have an open support ticket.
But this has been going on since at least June of 2025.

I'm close to giving up on ArcGIS Connectors and switching to another solution.
But we'd prefer to get ArcGIS working.

Our TS are saying the connector payload is an Object.
But it is expecting an array, please see attached image

We are stuck and I'm going to loose my mind.
Please help

Aaron

Error.png

AaronPDXPaul

I have verified this works.

All ArcGIS Connectors that are Actions work.
All ArcGIS Connectors that are Triggers are broke.

We can't move forward until esri resolves the issue.

Can anyone help me?

AaronPDXPaul

Our Organization settings prevent me from testing the HTTP Webhooks.

I feel as if I'm investing half a day each day trying different things.

Can anyone directly contact me at Clackamas County, OR?

CalvinHarmin

I am fairly ignorant when it comes to how webhooks actually work on the backend, so I rely on such connectors at this point for the creation and handling of webhooks.

My personal experience over the past year was that ArcGIS Connectors too frequently have inexplicable failures and I've changed a lot of my flow actions to API calls using an HTTP actions and the ArcGIS REST API rather than rely on the built-in connectors for things like querying, updating a record, etc.

I checked my test flow again that I created previously, and it is still not receiving webhooks when a feature is created.
After asking ChatGPT some instructions, I just now attempted to create a webhook receiver in power automate manually with "when an http request is received" automated trigger, but it does not receive anything either.
Next, I tried making a make.com webhook receiver and it also does not receive any webhook payload when a feature is created.
I also tried using the make.com Field Maps webhook connector (automatically creates webhook) and it also doesn't get a payload.
I also tried creating a webhook for a survey from hosted feature layer that I know is actively sending webhooks successfully through the Survey123 connector. That webhook I created manually with a webhook listener in power automate... does not receive a payload.
- I think the Survey123 webhook payload is sent from the client, rather than from the AGOL cloud? Maybe that's why that is succeeding currently?

Something ain't right. But I don't know if it has anything to do with the Power Automate government cloud necessarily since I can't get any webhook payloads delivered with external webhook receivers either (Make.com). I also could be doing this totally wrong...

AaronPDXPaul

This is excellent info
I am also investing a great del of time in discovering why the connectors or something is not working.

Esri has verified the connectors do work on a commercial environment
Unfortunately, according to esri, 80% of their customers are government.

I believe people like you and I have found other solutions besides the ArcGIS Connectors.
As they've been mostly unreliable, undocumented, and time consuming to keep it working.

Esri tech support can't assist.
Because they don't have access to a government environment.
Even though 80% of the customers calling are government.

I think @AkshayHarshe is our only hope.
As it seems noone else from the team monitors these channels or haven't had an opportunity to provide input.

I feel lost and in the cold

Aaron

Akshay Harshe

AaronPDXPaul

@AkshayHarshe Did you see the error from the Payload that our tech folks shared?

The payload returns an Object. But it's expecting an array.

Our Tech folks say this is why the Trigger never initiates

CalvinHarmin

I think it's important to clarify:
If your Tech folks review the power automate flow run history list:

Is it being triggered (i.e is there a recorded flow run) every time you would expect when a feature is created? Or was this flow screenshot isolated and there aren't really any other triggers occuring?

I have the impression that unless that flow is consistently triggering and halting due to the same error, that may have been an isolated glitch; maybe related to this overall webhook issue that is confirmed and being investigated now.

Since the only parameter for that automated trigger action is to select a layer from a pick list, there seems to be no way for anyone to misconfigure it.

Akshay Harshe

Esri has verified the connectors do work on a commercial environment
Unfortunately, according to esri, 80% of their customers are government.
I believe people like you and I have found other solutions besides the ArcGIS Connectors.
As they've been mostly unreliable, undocumented, and time consuming to keep it working.

@AaronPDXPaul I apologies for inconvenience. I appreciate you speaking your mind and it helps us improve. I acknowledge that recently there has been few events of outages. Access to GCC was bit of a pain since it needs certain requirements that non-US citizens can't fulfill them while some of the team members used to handle this left. That said, we have got a person to take this responsibility on and we are getting them set up.

Documentation site has been updates for all the ArcGIS for Microsoft products to have their own websites which gives us more autonomy, you should expect the doc to improve in coming release. This is something that is priority for us.

I hope you consider using the connectors in future.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.