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

[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

[AkshayHarshe · Accepted solution]

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.

[AkshayHarshe]

I want to update on this, I tested multiple hives and the webhooks on services.arcgis.com are affected at this moment. If you services are hosted on other hives such as services1/2/7  etc are not affected. I am working with the operations to figure out if there are any resources issue on. Thanks. 

[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.

[AaronPDXPaul]

I agree.
As I'm unable to replicate the error our IT shows in the screen shot.

I also don't understand how they got a response.
As the Flows never trigger.
So, no payload is ever generated.

We need someone with M365 knowledge and esri knowledge of what is going on.
Unfortunately, there doesn't seem to be anyone besides @AkshayHarshe who is willing to assist.
But @AkshayHarshe doesn't work on this team.

You are correct.
This was an isolated glitch.
I just wanted to share, as I really don't know enough on the back end to sat for sure

[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?

[AkshayHarshe]

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.