Latest Contributions by AkshayHarshe

@Jean-PhilippeLabrecque Get attachment action has not changed in a while, and always needed an attachmentID which is different than the objectID. Is it possible that you luckily had the same attachment id as the object id? Maybe new attachment was added to the feature and the old attachment was deleted instead of being replaced causing the failure. If you want to dynamically get the attachment ID using the attachment name, I recommend you to use Query attachment action and then use get attachment or get attachment from URL using the attachment ID/url returned from it. If your feature has multiple attachment then you may need to filter them out using Filter array then dynamically get the attachment using get attachment action. *Note that I removed the get attachment out of the For Each loop and added a formula to get the 1st item's 'id' in the filter array ... View more

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.   OR   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.  ... View more

@rlarose1 Thanks for sharing the error. I understand, I created an excel to keep track of all my connections and running tests.  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 I believe when the Multi-auth was rolled back by MS, the older version is probably authenticating with a newer connection but failing to refresh the token.  All my flows created with the original workaround are no longer working. The best case scenario is that this gets resolved on its own. I can't be certain without testing in our main env after the update. ... View more

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.   ... View more

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. ... View more

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. ... View more

@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.  ... View more

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

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 ... View more

@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. ... View more

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

Thanks for all your comments. Let go through these scenarios and see what I can find. I am certain that this morning the Reconnect and Switch account buttons are available on my disconnected connections in my environment but fix is still not rolled out so. Clicking them will open up the sign in page which will authenticate and work. I would recommend waiting (if that is an option for you) until the fix is rolled out to avoid additional work (if any).  According to MS the global roll-out takes 2-3 days for urgent pipelines such as these. ... View more

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. ... View more

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. ... View more

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.  ... View more