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; } } }

✅Behoben: Authentifizierungsproblem mit ArcGIS Connector (Release 2026.2)

Akshay Harshe

Mit der Version 2026.2 haben wir die API Key Authentication für den ArcGIS Connector eingeführt. Nach diesem Update beobachten wir ein Problem, bei dem bestehende Authentifizierungen als „verbunden“ angezeigt werden, aber Fehler in bestehenden Flows auftreten.<\/P>

Während der Vorabvalidierung haben wir eng mit Microsoft zusammengearbeitet und dieses Verhalten in unseren QA-Connectors nicht festgestellt; bestehende Flows mit älteren Verbindungen funktionierten auch nach der Änderung der Authentifizierung wie erwartet. Derzeit ist uns nicht klar, warum Verbindungstoken, die mit bestehenden Verbindungen verknüpft sind, ablaufen oder ungültig werden. Leider liegt dies außerhalb unserer Kontrolle zur Fehlerbehebung, da Power Automate alle Verbindungen verwaltet. Wir haben Microsoft eingebunden und ein Treffen geplant, um dies weiter zu untersuchen. Wir werden Updates bereitstellen, sobald weitere Informationen verfügbar sind.<\/P>

Außerdem haben wir festgestellt, dass bei betroffenen Verbindungen Optionen wie Reconnect oder Switch Account <\/STRONG>nicht verfügbar sind, was die Wiederherstellung für bestehende Verbindungen einschränkt.<\/P>***<\/STRONG><\/P>Änderung: Der folgende Weg ist erst verfügbar, wenn MS die Version 2026.2 mit dem Fix ausrollt.<\/STRONG>In der Zwischenzeit können die folgenden Schritte helfen, die Funktionalität wiederherzustellen. Dieser Prozess kann zeitaufwändig sein, wenn Sie viele Flows haben:<\/STRIKE><\/P>Öffnen Sie einen Flow, der nicht funktioniert.<\/LI>Wählen Sie eine ArcGIS-Aktion<\/STRONG>. <\/LI>Klicken Sie im linken Bereich auf Change connection<\/STRONG>. <\/LI>Klicken Sie auf Add New<\/STRONG>. <\/LI>Wählen Sie im Dropdown-Menü ArcGIS Online User Credentials<\/STRONG> und geben Sie einen aussagekräftigen Verbindungsnamen ein.<\/LI>Melden Sie sich bei Ihrer ArcGIS-Organisation an.<\/LI>Aktualisieren Sie alle ArcGIS-Aktionen und Trigger, um die neu erstellte Verbindung zu verwenden.<\/LI>Wenn andere Flows dieselbe Verbindung verwenden, aktualisieren Sie diese ebenfalls und speichern jeden Flow.<\/LI>Für Triggers/Webhooks<\/STRONG>, überprüfen Sie, ob der Webhook auf Ihrem Feature Service aktiv und funktionsfähig ist.<\/LI><\/OL><\/DIV><\/DIV>Wir verstehen, dass dies störend ist und danken Ihnen für Ihre Geduld. Entschuldigen Sie die Unannehmlichkeiten und vielen Dank für Ihr Verständnis.<\/P>***<\/STRONG><\/P>Update 1 am 9. Juni<\/STRONG><\/P>Es scheint, dass Microsoft versucht hat, das kürzliche Release auf 2026.1 zurückzusetzen, um die Auswirkungen zu minimieren. Es ist mehr als frustrierend, dass dies nicht etwas war, das wir angefordert haben, da viele von Ihnen bereits neue Verbindungen mit (neuer) Multi-Authentication erstellt und Ihre Flows aktualisiert haben. Letzte Nacht funktionierte keiner meiner Flows. Seit heute Morgen wurde ein Fix bereitgestellt, den ich teste. Ich werde alle informieren, sobald ich weitere Informationen habe. Vielen Dank für Ihre Geduld.<\/P>***<\/STRONG><\/P>UPDATE 10. Juni 16:15 Uhr<\/STRONG><\/P>Da Microsoft den Connector auf die vorherige Version zurückgesetzt hat, funktionieren die meisten bestehenden Verbindungen nicht mehr, es sei denn, man erstellt erneut eine neue Verbindung. Wir haben deren neueste Updates getestet, welche Folgendes beinhalten:<\/P>Unterstützung sowohl für Single Authentication (alte Methode) als auch Multi-Auth (neue dropdown-basierte Verbindungen), für bestehende und neue Verbindungen<\/LI>Ein Fix für das UI-Problem mit dem Verbindungsstatus<\/LI><\/UL>Soweit wir wissen, sollte dieses Update in wenigen Stunden ausgerollt werden.<\/P>Leider erfolgt das gesamte Testen mit einem temporären benutzerdefinierten Connector, den sie bereitstellen; dieser wird erst nach Validierung in der Microsoft-Produktion eingesetzt. Das bedeutet, dass wir den tatsächlichen Produktions-ArcGIS-Connector nicht direkt testen können. Dennoch bin ich optimistisch, dass dies die Verbindungsprobleme beheben wird oder zumindest eine Reconnect-Option bietet, wenn Tokens ablaufen.<\/P>Wir führen derzeit mehrere Szenarien auf Produktions-Connectors aus und werden die Ergebnisse später heute überprüfen. Realistischerweise könnten einige von Ihnen die Änderungen vor uns bemerken.<\/P>***<\/STRONG><\/P>Update am 12. Juni Mittag<\/STRONG><\/P>Laut Microsoft wurde das Update mit dem Fix in folgenden Regionen ausgerollt: Frankreich, Brasilien, Indien, Korea, Norwegen, Schweiz, Kanada, Australien, Asien, Deutschland und Südafrika. Sie sollten den neuen Authentifizierungstyp und die Version 2026.2 sehen.<\/P>***<\/STRONG><\/P>Wie erkennen Sie die Version 2026.2? <\/STRONG>

Erstellen Sie einen neuen Flow mit einem manuellen Trigger.<\/LI>
Fügen Sie eine Aktion Date and time format konvertieren<\/EM> hinzu.<\/LI>Verwenden Sie die Formel `utcNow()`.<\/LI>Führen Sie den Flow aus.<\/LI>Klicken Sie im Lauf auf die Aktion Date and time format konvertieren<\/EM>, dann wählen Sie Show raw outputs<\/STRONG>. <\/LI>Im Header-Bereich sollten Sie die arcgis_connector_version<\/STRONG>-Angabe sehen.

Alternativ erhalten Sie beim Erstellen einer neuen Verbindung ein Dropdown-Menü zur Auswahl zwischen User login und API Key.<\/LI>

style="width: 400px;">

<\/span>

ODER<\/STRONG><\/P><\/span>BEHEBUNG<\/H4>Stellen Sie sicher, dass Sie nicht in einem anderen Tab bei ArcGIS Online angemeldet sind (damit das erneute Verbinden die Anmeldedaten nicht aus dem lokalen Speicher übernimmt, ohne Sie zur Anmeldung aufzufordern). Im Zweifelsfall verwenden Sie ein Inkognito-Fenster, um sich bei Power Automate anzumelden.<\/LI>Öffnen Sie den Verbindungsdialog<\/LI>Um die Verbindung zu finden, die mit einem Flow verknüpft ist, klicken Sie auf die 3 Punkte vor der Verbindung und wählen Eigenschaften anzeigen<\/LI>Überprüfen Sie den/die Flows, die diese Verbindung verwenden, und bestätigen Sie, dass der Flow, den Sie beheben möchten, enthalten ist<\/LI>Klicken Sie auf Erneut verbinden; es sollte ein Anmelde-Dialog geöffnet werden<\/LI>Wenn Erneut verbinden nicht aktiv ist, wählen Sie Konto wechseln.<\/LI><\/OL>FALL 4<\/H3>Diese Verbindung wurde mit dem Workaround in diesem Beitrag<\/STRONG> unter Verwendung des 2026.2 Multi-Auth-Updates erstellt, bevor Microsoft es zurückgenommen hat. (zwischen dem 3. und 9. Juni)<\/P>Beide Verbindungen, die mit dem Verbindungstyp OAuth2 und API-Schlüssel<\/STRONG> erstellt wurden, begannen automatisch ohne Eingreifen gegen 8:20 Uhr EST am Sonntag, den 14. Juni zu funktionieren.<\/P>Der Flow begann automatisch zu funktionieren und Sie müssen nichts weiter tun<\/LI>Wenn die Verbindung fehlgeschlagen ist, versuchen Sie die Behebungen in Fall 1-3, wobei das erneute Verbinden der letzte Schritt ist<\/LI><\/UL>Ermitteln Sie, wann sie zu funktionieren begannen<\/STRONG><\/P>Öffnen Sie den Flow<\/LI>Klicken Sie unter Ausführungsverlauf auf Alle Ausführungen<\/LI>Filtern Sie nur fehlgeschlagene Ausführungen über das Dropdown-Menü oben rechts.<\/LI>Sehen Sie alle fehlgeschlagenen Ausführungen ein.<\/LI><\/OL>Siehe Beispiel unten<\/P><\/span><\/span> <\/P>Ich hoffe, das hilft. Bitte lassen Sie mich wissen, wenn Sie andere Probleme haben, die nicht behoben werden können. <\/P>Vielen Dank an alle für ihre Geduld. <\/P><\/DIV><\/DIV><\/DIV>

Finde mehr Beiträge mit dem Tag

Kommentare

Annie_K

@AkshayHarshe Are there any defects in the Esri system that I can attach to an existing case that presents with these issues?

Thanks!

Annie K (Esri Support)

ISP_graynic

@AkshayHarshe thank you for your frequent updates on this issue, it was good to know ESRI was working on this from the start of the issue!

I re-connected our connections after the rollback from 2026.2 to 2026.1, and they seemed to have been working fine over the weekend so hopefully we are good to go now!

Akshay Harshe

Hello Everyone. First of all thank you for your patience. Microsoft confirmed that the Fix with the update has been rolled out to the US this morning (Sunday June 14, 2026). I was able to test multiple scenarios. Here is a summary of my testing and cases with screenshots on how I was able to fix any issues I experienced. I will keep monitoring my flows for any errors.

Connections created	Comment	If working	If they are broken
Pre June 3 before any issues stated, Version 2026.1 or older	By stroke of luck if you did not touch any connections these should re-authenticate with no issues. For possible issues and fixes refer CASE 1, 2, & 3	Should continue to work	Try not to reconnect at first, instead try this: Edit the flow that is failing the flow should fix any errors, then exit the flow without saving. If 1 doesn’t work then try changing connection back and forth on actions that are in error state. Try reconnecting existing connection or Switch accounts
Using the workaround posted above (between June 3-9) These connections created using the new Multi-Authentication in 2026.2 before Microsoft roll-back on June 8-9	These connections authenticated through both OAuth2 and API Key Should automatically start working. Refer Case 4	Check when the start working	Try editing the flow (don't make changes) Save. They should start working
After the roll-back (2026.1) These are essentially same as the last release if you created them after the roll back (between June 9 - 14ish) and only saw single-auth to connection	These should continue to work. Refer CASE 1-3.	Lucky	Try reconnecting or switching account, They should show the sign-in dialog

Case 1

Old connection Pre June 3rd that I reconnected after the roll-back (after June 9). The flow is working as expected but when I edit the flow I see this it is in the error state

FIX

Open the flow.
Open the action with error
Click change connection
Select a different connection
Re-select the original connection.
Save the flow

CASE 2

The Flow was failing with a time out error for no real reason. This is using the connection created after roll-back on June 9 (2026.1)

Open the flow in Edit mode to show no errors then closed the flow without saving fixed this issue. If this doesn't work try saving.

CASE 3

If you see your connection is still connected but when using it in a flow throws following error.

FIX

Make sure you are not logged in to ArcGIS Online in another tab (so the reconnecting won't pick up the log-in details from local storage without asking you to log in), if in doubt use a incognito window to log into Power Automate.
Open Connections dialog
To find the connection associated with a flow click on 3 dots in front of the connection and click View Properties
Check the flow(s) using that connection and confirm it includes the flow you are fixing
Click Reconnect should open sign in dialog
If you don't see Reconnect active choose Switch account.

CASE 4

This connection created using the workaround in this post with 2026.2 multi-auth update before Microsoft rolled it back. (between June 3 - 9)

Both Connections created using connection type OAuth2 and API key started working automatically with no intervention at around 8:20AM EST on Sunday, June 14th

Flow started working automagically and you don't have to do anything else
If the connection failed then try fixes in Case 1-3 with reconnecting being the last

Find out when they started working

Open the flow
Under run history click All Runs
Filter only failed runs using the dropdown on the top right corner.
See all the runs that failed.

See example below

I hope this helps. Please let me know if you are experiencing other issues that are not fixable.

Thank you everyone for their patience.

Richard_Caprio

Hello, just reaching out prior to the Monday morning start....

Without refreshing any existing ArcGIS Connections since the end of business on Friday, we are seeing flows successfully running today (Sunday 5PM New Jersey EST).

Any word from Microsoft regarding what may have been rolled out?

We will re-evaluate in the morning and can provide more details.

rlarose1

I'm having trouble keeping track of which connection is which at this point but the one that fails for sure every 30 minutes is my "named" connection that I created after things initially failed and before the roll back. It gives this error if I don't manually reauthenticate (using it in a flow doesn't work to refresh it): Failed to retrieve dynamic inputs. Error details: 'The dynamic operation request to API 'arcgis' operation 'QueryFeaturesSchema' failed with status code 'BadRequest'. This may indicate invalid input parameters. Error response: { "message": "Fetching data from www.arcgis.com failed. This is usually caused by an invalid authentication token that has expired. Please reauthenticate to continue. Error message: undefined 498: Invalid token.", "success": false }'

Akshay Harshe

Microsoft l confirmed that these regions should see the update and I can confirm that for Canada. Unfortunately for folks experiencing this issue it appears to be the case until the update is rolled out to the US. I am monitoring this over the weekend and I will keep everyone posted. Please notify me in a DM if your connections are still doing this after the update roll out is complete.

Question for everyone: this happens even if you create a new connection or only for existing connection? what is the error that you get? I am trying to isolate issue of dropped connections to see if it is different than this so this info will surely help. My flows with different frequency and different connections are either working or failing.

Akshay Harshe

If this is intermittent like this this could still be related to existing issue at hand. The rollout hasn't been started to US regions yet. I can't say for sure but Power automate server must have load balancers to send load to different stations which could be the cause of intermittence. Unfortunately, test my flows are either broken or working.

Once refresh token is issued by ArcGIS online it is valid for 2 weeks the connector just acts as a middle-man that routes these requests between Power Automate and ArcGIS Online. There is no reason for Power Automate loose the token(and connection) for 2 weeks once issued by ArcGIS Online. This is why it makes me think that it is still the same issue, and why I was asked to create a recurring flow like this could somehow circumvent any issues of dropped connection. Apologies if it hasn't worked for you.

MitchellGrafstein

@AkshayHarshe wrote:
Update June 12 Noon
Update with the fix is rolled out to following regions according to Microsoft: France, Brazil, India, Korea, Norway, Switzerland, Canada, Australia, Asia, Germany and South Africa. You should see the new authentication type and 2026.2 version.

Does this mean that the rest of the regions are still waiting on the update and should continue to expect dropped connections? Did your timed flow continue to keep your connection alive?

Akshay Harshe

Update June 12 Noon

Update with the fix is rolled out to following regions according to Microsoft: France, Brazil, India, Korea, Norway, Switzerland, Canada, Australia, Asia, Germany and South Africa. You should see the new authentication type and 2026.2 version.

Akshay Harshe

@KevinBerger5 yes, the error matters for us, we can try and look at the telemetry to see compare that and see if there is a different issue than this one.

TL2

I set up a Get Item Information to run every 2 minutes and it failed on the 15th run.

KevinBerger5

Does the error even matter? As soon as refresh the connector it the flow works again. So, using the flow to refresh the connector does not seem to work.

MeganHicks

Hi Jacob, would you be able to share more about how you set up a flow to refresh the connection? This would be very useful for my organization too!

MichaelPierceVAIDSP

Within the first hour, it failed. We run enough transactions all day long that I was not convinced this was going to help. We even see cases where there are Successful results in between Failed ones. So the token issue seems to fade in and out. We're trying to lower the timer to 10 minutes, but again, we're running API calls almost non-stop all day long and see this issue.

Akshay Harshe

Thanks for your comment. What is the error that you are getting?

KevinBerger5

This does not work. The flow ended up failing after about 30 minutes. I even reduced the recurrence time to two minutes.

Akshay Harshe

I am testing the Connection being dropped every 20 min - 1 hour so far my connections are working. I think this is related to the main issue as the token exchange mechanism hasn't changed.

If you don't already have something like this set up. Maybe try following

Create a New flow on Recurrence to run every say 20 minutes
Add Get data from Feature layer action. Use the connection you have authenticated. Configure the action to return 1 or 2 records using "Result record count" option.
Repeat step 2 for every connection you want to authenticate.

See if this helps.

I have updated the Main text for additional information. I will post another update soon. And I will have to source that beer from Microsoft! Lets name it MS I-PA

JacobMyers

Update! We switched it to every 5 mins and that seems to be the sweet spot for our environment 😎

MichaelPierceVAIDSP

Do you have any updates for us? My connections are dropping every hour despite being recreated/reauthenticated - across 3 tenants and 20+ flow - a system that keeps our CRM and Workforce in sync is a mess. Day 9 and we cant clean up this mess fully until we have a working pipeline again.

JacobMyers

We updated our refresh flows to fire every 29 mins and send an email if the connection failed. Sadly it was not solving the issue and still failing - We even switched it to every 10 mins and still no luck 😞 Hopefully we all get a beer after this week of fun haha

Theisen

Could you share this flow that notifies you when your connection is down? That would be very useful. Thanks.

RachelAbernethy

Thank you @AkshayHarshe and everyone else for your comments in the past day.

As a recap, we did change our connections last week so those broke again this week when the version was rolled back. We haven't made any changes again this week in the hope that another update might fix the connections we now have in place.

We have just created a new flow to check the version, based on the steps in the article above, and can confirm that we are still on 2026.1. We're based in Ireland.

We will check again on Monday but at that stage we will need to take some sort of action to get the environment back up and running again.

TL2

Looks like the "New" connections made after the release need to be refreshed every 30 minutes. I have a flow that alerts me when the connection is down and that's my pattern. We have many important flows so I have been refreshing every 30 min. Hopefully we get the patch soon.

Oh well, these things happen. Thanks for the consistent communication on the matter. ESRI can buy me a beer at Dev Summit 27 for this headache.

KevinBerger5

Hopefully the June 2026 ArcGIS Online update will be tested with the updated Power Automate, so we all do not have to go through this again in another couple of weeks.

Akshay Harshe

@SharonUngerer_DNREC I am certain that the fix isn't yet rolled out to North America. so you are probably experiencing the breakage that happened after MS's roll back.

NICK_COG

After changing all of my connections the day this was posted, I am finding myself having to change the connection to any flow that I need to edit.

Any flow that I can leave as is, still seems to be sending emails up until 13 minutes ago. But I have just coincidentally had three requests come in for updated logic in some of our flows, and I cannot do anything until I cchangethe connection. Here is the error I am receiving on the brand new connection from earlier this last week.

Failed to retrieve dynamic outputs. As a result, this operation's outputs might not be visible in subsequent actions. Error details: The dynamic operation request to API 'arcgis' operation 'WebhookPayloadSchema' failed with status code 'Unauthorized'. This may indicate invalid input parameters. Error response: { "error": { ------- "message": "The response is not in a JSON format.", "innerError": "Cannot read server response." } }

Akshay Harshe

James, I understand you sentiment but given the scale of the impact this wasn't an option.

JacobMyers

@JamesWheaton4 @ISP_graynic I might be wrong but this seems to be tied to the 404 error, where it completely breaks your webhook. It hasn’t happened to any of my flows yet, but it has happened to my colleague. When you fully create a new connection and redirect your triggers to that new connection, you’ll need to reconfigure your webhook settings back to their original state (for example, enabling triggers to fire on edits). This also forces users to download a new Survey update in Survey123.

ISP_graynic

Created a new copy of the flow and re-connected the ArcGIS Connector which seems to bring a new webhook in and the Settings page is showing webhooks now. Not sure what that was about but with all the changes going on wouldn't be surprised if it was related. Thanks @JamesWheaton4!

SharonUngerer_DNREC

As of this morning this fix is no longer working. After I update the connection by adding a new one, publish, and go back to My Flows page I am hit with the error below:

There's a problem that needs to be fixed to trigger this flow. To see more details, open the Flow Checker.

I am using the ArcGIS - When a survey is submitted trigger. I have the government suite of Office 365 and we use OKTA for IAM. This flow is using an ArcGIS Online account using the same email/login as my Office 365 account.

Essentially I am in some loop where I update the trigger and its fine but after i close the Edit screen for that flow the trigger is broken again. I can go back in and add a new one. But its broken as soon as I go back to my flows. I have 3 duplicated connections now because of this and flows actively failing.

JamesWheaton4

JacobMyers said it changed his webhook settings here: https://community.esri.com/t5/arcgis-connectors-for-power-automate-questions/power-automate-connections-failing/m-p/1706021#M1348 not sure if its related

ISP_graynic

Too add on top of all these issues, is anyone else not seeing their Webhooks in the"Settings" page for a survey on the Survey123 website? The flow is active and has active connections to this survey but the Webhooks section seems to have disappeared all of a sudden and I can't update the webhook settings?

Screenshot 2026-06-11 at 9.42.41 AM.png

JamesWheaton4

Also, can you please do these updates on a Monday or Tuesday instead of breaking everything before the weekend.

Willie_C

Yesterday's update seems to fix the issue for my GCC tenant. I can see the switch account option and flow were actually running late yesterday afternoon and I've been rerunning some of the flows which failed previously, and they all ran successfully without issues.

ISP_graynic

We are getting this error now. We have several public safety flows that are broken and need to be running. Can ESRI dedicate additional resources to this?

Fetching data from www.arcgis.com failed. This is usually caused by an invalid authentication token that has expired. Please reauthenticate to continue. Error message: undefined 498: Invalid token. Upgrade

JamesWheaton4

These updates and roll backs keep making things worse. what are yall doing over there....stop it

Theisen

@AkshayHarshe I am still not seeing this update in my current flows. I still see the same error message and when I create new flows with the arcgis triggers, I don't see half my layers (which v2 fixed). I only see layers up to ones that start with "F". Are there plans to re-instate the "My Content" and "My Organization" parameters?

No Reconnect option. Seems like all my flows using this connector are dead and need to be completely recreated.

MichaelPierceVAIDSP

This morning, all connections went bad - refreshing them only keeps them active for a very short time - 10-15 minutes before failing again.

This is a train wreck - incredibly frusturated that this has been impacting our production systems for over a week now.

Jamie_Leitch_CNF

A new connection I created last week seems to be working, but when I create a new connection, the connection gets created but any flow that uses it produces the invalid token 498 error.

TL2

Ever since the roll back our connections have been terrible, they keep failing even after we switch accounts.

erica_poisson

I was able to use the "Switch account" option, which is now available when I look at the ArcGIS connector under the "Connections" menu. My ArcGIS token refresh flow then ran for the first time since last week.

Hopefully this solves the issue. Do you know if this is a long-term fix, or if this issue will pop up again when Microsoft re-releases 2026.2?

Jean-PhilippeVandal-Labrecque

The ArcGIS connector authentication issue appears to be resolved and the API connection is now working. However, the Get attachment content action still fails, preventing the flow from processing and transferring attachments to SharePoint. Issue remains unresolved.

ISP_graynic

@AkshayHarshe our flows are not working again this morning and causing Authentication errors when running. This is with the ArcGIS Connection that was updated following the workaround instructions last week when things first broke. When I went to "re-connect" this time, it gave me a new notification/message that I hadn't seen before and after proceeding through that it re-connected and I was able to re-run it. I'm hoping this is the last and it doesn't lose connection again as we have several critical flows that keep breaking with Connector changes.

RachelAbernethy

Thank you so much @AkshayHarshe for the updates and support - I will check the flows in the environment we are working in today and share any feedback here.

Thanks
Rachel

Akshay Harshe

Update

Hello everyone,

Since Microsoft rolled back the connector to the previous version, most existing connections are no longer working unless you create a new one (again). We’ve completed testing their latest updates, which include:

Support for both Single Authentication (old method) and Multi-Auth (new dropdown-based connections), covering both existing and new connections
A fix for the UI issue with connection status

From what we understand, this update should begin rolling out today in a few hours.

Unfortunately, all testing is done using a temporary custom connector they provide, which is only deployed to Microsoft production after validation. This means we can’t test the actual production ArcGIS connector directly. That said, I’m optimistic this will resolve the connection issues, or at least provide a Reconnect option if for some reason ArcGIS tokens are expire.

We have multiple scenarios currently running on production connectors and will review those results later today. Realistically, some of you may notice the changes before we do.

CRossNSDA

We’ve had the majority if not all of our flows are still impacted. Had some intermittent working runs but not all not working again. This has had significant impacts to our operations.

JoeEastman1

Just wanted to share that we are also seeing the exact same issues as everyone else. Tokens keep expiring and have impacted a significant amount of our workflows.

MichaelPierceVAIDSP

Our connections that we reset in 3 environments all failed today.

TL2

Our connections have been intermittently failing all day. We have had to reset the account about 10 times. Sometimes it works and sometimes it fails.

erica_poisson

I am still seeing no change in my ability to refresh my existing connection. I am a GCC Microsoft customer, if that is relevant at all.

Screen grab of Power Automate "Connections" with the ArcGIS Connector's options expanded. No "Refresh" option is available.

Theisen

Sounds good. All of my flows are still broken so we will be waiting for your response.

Akshay Harshe

Update

It appears that Microsoft tried reverting the recent release back to 2026.1 to minimize impact. It is frustrating to say the least, that this is not something we asked for to happen as many of you have already created new connections with (new) multi-authentication and updated your flows. Last night none of my flows were working. As of this morning they have provided a fix that I am testing. I will update everyone after I have additional information. Thank you for your patience.

Theisen

I am unable to even create new flows now using arcgis connectors. I get the attached error and no options to switch accounts or re-authenticate. I have deleted triggers and actions and tried to replace but I get the same message. Anyone else seeing this issue?

Screenshot 2026-06-09 162644.png

TL2

Seems like there was a release around 1 pm MDT. It fixed the old connections - allowing us to Switch Accounts. It broke our new connections, but those were fixed quickly with Switch Accounts as well.

Akshay Harshe

I would like to know what errors you are getting since I still don't see these. If possible can you DM me screenshots of the error, the region you are and your environment id. So I can ask directed questions to MS.

Willie_C

I encountered the same issue, I don't have the option to switch account and when I try to create new connection in an existing action, it will just give me a red exclamation mark. I have tons of flows relying on this connection so I'm hoping MS is able to fix it asap.

RachelAbernethy

Hi everyone - I just shared this on another post about this issue (https://community.esri.com/t5/arcgis-connectors-for-power-automate-questions/power-automate-connections-failing/m-p/1705936/thread-id/1340) but thought I better ask here too.

We encountered this issue in a customer's environment last week and updated the connectors to resolve the issue as explained in this post. The Power Automate flows ran successfully yesterday but are failing today. Should we be carrying out another fix or should we wait for an update from Microsoft or Esri?

Thanks everyone for sharing your thoughts and updates here, it is really helpful.

Thanks

Rachel

Erwinvan_Veen1

Sometimes the old connection does show the 'Switch account' option and sometimes it does not. I did not really look for a pattern to find the reason is sometimes doesn't show. All my flows should be using the new connection, although the old connection still shows all the flows it used to be in. It doesn't seem to be updated in which flows it is used. Quite confusing. I am afraid to delelte the connection enterily, because it may perhaps cause some unexpected behaviour.

I am unsure where I can find the connector version. In the action 'Get data from feature layer' for example I did not see this particilar part. Not in code view at least of either the edit-mode of the flow or in a log from a previous run. Nor did I find the version in the Connections in PowerAutomate. If you could point me in the right direction, that would be great.

Akshay Harshe

@Erwinvan_Veen1 Thanks for posting. Is this an older connection that you tried reauthenticating using switch account and worked? The connector version in the headers points to 2026.1.

"arcgis_connector_version": "ArcGIS 2026.1.0 2026.01.29 1769704901160 887a30"

They might be making some changes but we are yet to receive any update on our questions for what the fix is and how it is going to affect everyone. You being in EU zone helps as the product team is in NA. I have set up a few flows to test all the new 2026.2 connections. I hope they break the new connections everyone created.

Nehmen Sie an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registrieren Sie ein kostenloses Konto.

Schnellzugriffe

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