✅Resolved: Authentication Issue with ArcGIS Connector (Release 2026.2)

[AkshayHarshe]

With the 2026.2 release, we introduced API Key Authentication to the ArcGIS Connector. Following this update, we are observing an issue where existing authentications appear as “connected” but shows errors in existing flows.

During pre-release validation, we worked closely with Microsoft and did not encounter this behavior in our QA connectors existing flows with older connections continued to function as expected even after the change in authentication. At this time, it is unclear to us why connection tokens associated with existing connections are expiring or becoming invalid. Unfortunately, this is out of our control to troubleshoot as Power Automate maintains all connections. We have engaged Microsoft and scheduled a meeting to investigate this further. We will provide updates as soon as more information becomes available.

Additionally, we’ve noticed that in affected connections, options such as Reconnect or Switch Account are not available, which limits recovery for existing connection.

***

Change : The Following pathway is not available until MS rolls out the 2026.2 version with the fix.

In the meantime, the following steps can help restore functionality. This process can be time-consuming if you have many flows:

1. Open any flow that is not working.
2. Select an ArcGIS action.
3. Click Change connection on the left pane.
4. Click Add New.
5. Choose ArcGIS Online User Credentials in the dropdown and provide a meaningful connection name.
6. Sign in to your ArcGIS Organization.
7. Update all ArcGIS actions and triggers to use the newly created connection.
8. If other flows are using the same connection, update those as well and save each flow.
9. For Triggers/Webhooks, verify that the webhook is active and functioning on your Feature Service.

We understand this is disruptive and appreciate your patience. Apologies for the inconvenience, and thank you for your understanding.

***

Update 1 June 9

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.

***

UPDATE Jun 10 4:15PM

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 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 when tokens 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.

***

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.

***

How do you know you are looking at 2026.2?

• Create a new flow with a manual trigger.
• Add Convert date and time format action.
• Use formula to add `utcNow()` 
• Run the flow
• In the run click on the Convert date and time format action then select Show raw outputs
• In the headers section you should see the arcgis_connector_version
  
  Alternatively, you click create new connection it should give you a dropdown to choose between User login and API Key.

***

June 14th Morning

The fix is rolled out to the US from Microsoft, please confirm you are on version 2026.2.

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

1. Open the flow.
2. Open the action with error
3. Click change connection
4. Select a different connection
5. Re-select the original connection.
6. 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

1. 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.
2. Open Connections dialog
3. To find the connection associated with a flow click on 3 dots in front of the connection and click View Properties
4. Check the flow(s) using that connection and confirm it includes the flow you are fixing
5. Click Reconnect should open sign in dialog
6. 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

1. Open the flow
2. Under run history  click All Runs
3. Filter only failed runs using the dropdown on the top right corner.
4. 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. 

[NICK_COG]

When I click add new connection, nothing happens. I had to remake from the connections screen.

Also, I still am not able to provide a name for my connection, I am hoping it is just something I am missing. I click sign in, pass in my credentials, and then am redirected to the beware of phishing screen. After that I am brought back to the connector page and see no option to rename the connection there.

[NICK_COG]

Additionally, 

Still having issues with some flows even after creating a new connection and updating them.

On this, with the connecter to watch for edits to a layer, I am getting this new error when I try to save a flow with the new connection (and have verified it is able to see the service):

The above was caused from downstream actions that also needed their connections refreshed to ArcGIS as well, that was in the initial post, sorry about that.

[Erwinvan_Veen1]

This is extremely unfortunate. This suddenly affected some 20 separate flows we use in production due to which a large number of e-mails were not sent, data was not being updated, coworkers not being notified and so on. In each flow, multple ArcGIS connectors were used, so I suddenly had to update near 50 actions. Somehow these kind of situations occur when it is most inconvenient.

If there is any way we can see when updates to connectors and actions are scheduled, that would be great. That would allow us to monitor our flows more closely and anticipate any errors. So, if there is any newsletter or other channel I can use to be notified, please respond.

Luckily, the 'add new' is a great addition and did resolve this issue. Although it being a lot of work to be done in a short amount of time, currently we do no longer have issues.

Sidenote:

Another unfortunate issue with PowerAutomate itself is that it is hard for us to be notified by failing flows. I noticed this purely by chance. I understand this has nothing to do with this particular issue, however this add to our difficulty handling these unexpected issues.

[ISP_graynic]

Thankfully found this thread after trying to figure out why the "Reconnect/Switch Account" option wasn't available on the Connector this morning and we were getting "Unauthorized" errors on our flows. We did the fix listed by @AkshayHarshe for now though and it seems to work. Will be subscribing to this thread for any updates. 

[ArthurSmith2]

Please advise on next steps for a fix... we are waiting to implement the workaround suggested above as it may require not only changing the connection on each ArcGIS action, but updating all other actions downstream that use dynamic content.  This becomes a huge task with multiple flows with 100+ actions.  Waiting for more info and a potential fix from Esri and Microsoft before attempting this.

@ISP_graynic and @Erwinvan_Veen1 did you have to update all dynamic content in downstream actions after implementing the workaround?

[ISP_graynic]

I had to update the connection on all actions that use the ArcGIS Connector but didn't have to do it for any dynamic content resulting from the connection. Updating the ArcGIS Connectors seemed to automatically update the dynamic content used by different actions without any problem. We did have several actions however within the same flows and had to make sure each one was updated. 

[AkshayHarshe]

@Erwinvan_Veen1 I understand your frustration, it is quite unfortunate. Thanks for the suggestion, I will also recommend subscribing to Power Automate community though it might be too many emails for some. I usually try to post a community blog for upcoming features once we see the new changes.

We submit our Connector updates to Microsoft and once they are gone through final approval and testing,  we don't know when they will roll it out. Different regions in the globe will receive the updates at different times usually North America is the last one. This is why planning the release of documentation and such notification bit challenging as some of our submissions took months to roll out in the past, especially if they have black out dates like they do for FIFA world cup in this year.

Maybe I will try to write community blog updated as soon as connector submission is finalized, I will also float the idea of a newsletter to our PM and see if we can make that happen. It might be early and not align the actual roll out but could prepare everyone for what's coming.

That said, this was the exact scenario we were hoping to avoid and had tested thoroughly using custom connectors. I am not certain what is different when MS updates the production connectors, why the connector shows connected and token is invalidated.

[AkshayHarshe]

You shouldn't need to update the dynamic content, just replacing the connection with new on should work. As long as it has access to layers in the flow. We are working with Microsoft to see what went wrong and if there is a cleaner fix. If you have any critical flows please go ahead and implement this workaround. 

[SunshineLuke90]

Appreciate the context Akshay.

My organization has had a similar experience to @Erwinvan_Veen1, where we have many mission critical workflows built on top of power automate ArcGIS connectors. This isn't the first issue we've had with power automate connectors breaking, and I would really like to see a Root Cause Analysis once this issue is resolved, as we may have to re-evaluate how Power Automate fits into mission critical software, and whether Power Automate will offer the reliability that we need for our workflows.

Again, thank you for the transparency and quick response on providing a workaround, and for the insight into how the Power Automate connectors are developed and published. 

Thanks,

[michael_vetter]

Thanks for this post. Like most that have posted, I have many workflows that involve Power Automate and I was able to update the AGO connection to get the flow to work. However, I've noticed that the performance is very sporadic. Since about noon CT, most flows have stopped working all together while a few occasionally work. They were working fine this morning. Any troubleshooting ideas are welcomed.

[AkshayHarshe]

@SunshineLuke90 Welcome. I am here to help and bring clarity to issues. We had a few of these instances since last year from Azure outage to ArcGIS Online outage, and none of them were issues/bugs with the ArcGIS Connector directly. Connectors heavily dependent on ArcGIS online, Enterprise and sits inside of Microsoft system which adds even more challenges to resolve issues that are out of team's control. I hear your sentiments, and regardless of the cause your flows are disrupted. We are still working to find the root cause, because we need to understand why this happened after all the previous testing and can this happen again.

[SunshineLuke90]

@AkshayHarshe, Totally understand. The power of having ArcGIS Connectors within Power Automate is not lost on our team, and like you mentioned, with so many interconnected systems, often the issue is outside of Esri's control. At the end of the day, my primary concern is just to ensure that the most mission critical workflows that our organization rely upon are built on the strongest possible foundation.

Thanks,

[Rastislav_Minárik]

Hello, several of our procedures have also failed. This error affected our report generation as well as notification emails. We believe that this error will be fixed ASAP.

[pangue]

Hi, thank you for the work around. I have applied this to couple dozen flows and it has worked. However, it does not appear to work for flows that dynamically load the feature layer URL. I have several long running flows that dynamically load 50+ feature layer URLs, where the feature layer URL is inputted via a calculated field through a reference list. I.e. one flow runs same process on 50+ feature layer URLs. 

With the new connector I receive this message on Publish: 

Flow save failed with code 'DynamicOperationRequestClientFailure' and message 'The dynamic operation request to API 'arcgis' operation 'GetDynamicSchemaForCreateUpdateFeaturesAction' failed with status code 'BadRequest'. This may indicate invalid input parameters. Error response: { "message": "User does not have create permissions on the selected layer. Please check your permissions and try again. You can also select another layer in the list.", "success": false }'.

Logically I am struggling to make sense of it, as the connector should not yet be able to check for the Schema as the Feature Layer URL is not inputted until the flow runs. 

[JamesWheaton4]

All our flows have broke because of this update...

[tschrage]

I'm anxiously awaiting a solution as well.

[KeniaFritz]

It worked for me after few attempts, tweaks and 3 different error messages. My flows seem to be working now...after a mini heart attack! Thanks.

Best luck everyone!!

[KylaCupp_SBY]

Hey, 

If you have your flow in a Solution you can create a error handling flow. None of our flows are emergency status so we just have it run once a day and if nothing is broken we get a trivia fact in teams and if something failed it lists the flow and the error in the email. I'm sure there is a better way to set this up where it's triggered when a flow fails but this has been really helpful for us.  It leverages the Dataverse flow run table. Happy to share more info you have questions. 

The downside of  having flows in solutions though is that it's even harder to fix when an ESRI update accidentally breaks all of the connections 😅.

[erica_poisson]

Hello - 

I am very interested in a cleaner solution. We have over 20 flows which depend on this Connection, including our auto "refresh" connector which keeps the token for this connection up to date and all flows healthy. Please keep this thread updated with findings from your work with Microsoft, as I (and I am sure others) might wait for more information before implementing the extremely time consuming workaround you've outlined.

Erica

[AkshayHarshe]

An update to everyone following this thread. We tested upgrade process once again in our development environment using custom connector (connectors are developed using custom connectors) and we could confirm that our older connections continued to work. This means production connections are handled differently than connections created using custom connector. 

Since yesterday afternoon, I can also see Reconnect and Switch account buttons on my connections but both these options don't work and internally throws an error. I believe that might be the case for everyone. Let us know if you see something else and I would like to gather all other behaviors.

We have submitted our findings to Microsoft and their product team is investigating the cause following issues

1. Why connections show connected but not work
2. Why can't we re-authenticate or use switch accounts on old connections

Unfortunately, no resolution yet but I will keep you posted.

[GIS_Admin]

@AkshayHarshe when I try your method of fixing the connections, I get an error. I can successfully create the new ArcGIS connection, but I try to change the action in a flow to the new connection I get the error:

"There was a problem using the 'GUID-removed for safety' connection to access 'ArcGIS'. Try again, and if the problem persists, try checking to see if the current connection should be fixed, switching to a different connection, or creating a new connection."

[erica_poisson]

I do not see the option to Reconnect or Switch account when I go to Connections and try to manage it. I do still see the Switch option when looking at my Survey123 connection.

[AkshayHarshe]

If you are using the Survey 123 Green connector then it is no longer being maintain so it shouldn't have any changes. Thanks for letting me know that you still can't see Reconnect and Switch account option. I have seen that still happen to my colleague.

[AkshayHarshe]

 @GIS_Admin That is interesting, I haven't seen that error before. Can you DM me screenshots on how you are creating the connection and the error you are getting? 

Are you creating a new connection in the connections tab or from within the flow? Also try using an incognito browser window to log in to Power Automate. Sometimes browser cache can be sticky like that. 

[rlarose1]

I just wanted to offer an option that has helped us not have to immediately change every single arcgis connection like we've had to do in the past. We implemented dev and production environments in power automate, so you can deploy the dev flows to production using a pipeline, which lets you change your connections during that deployment. When everything was broken yesterday, we just had to create one new arcgis connection in our production env and then chose that connection when re-deploying and it fixed everything. Our dev environment is still broken right now since I'm waiting to see if this gets fixed without having to spend a lot of time switching our connections, but it was great for fixing things in production quickly.

[TL2]

But your flows have to be in a solution, right?  Thats the main point, use a solution.

[KylaCupp_SBY]

It does update the connector if you redeploy but if you used fetch updates or update a layer all those actions need to be replaced because of the schema change from my understanding. That’s how we got our most complicated flows working. 

[rlarose1]

Yeah they have to be in a solution but can you update the connections in a solution all at once? I wasn't able to get that working yesterday. I was trying to change the connection source of the connection references in the solutions but it wasn't working for me. 

[rlarose1]

I'm not sure I didn't have to update any individual actions or the triggers

[AkshayHarshe]

Here is another update, Microsoft has identified the issues and tentative ETA we were given from them is June 9th. We don't know what exactly is the fix that is being implemented right now but hoping to get to know soon. I will let everyone know if there is any deviation from the ETA given. Thank you for your patience.

[NICK_COG]

Kyla,

I have been trying to get this set up on my end but our IT Sys Admins are unable to provide me with the correct permissions to use this flow. What permissions does your microsoft account have to be able to access the dataverse flows? 

This is something I have been wanting to set up for a while, if I could give clear instructions to the sys admins it would be a quick set up.

Thanks for your post. 

[gis_KIWI4]

@AkshayHarshe - We have a followed the steps and managed to restore the flows. It worked well for a day or two and now it's all broken again. Any advice on making this a more permanent fix? 

 

[Erwinvan_Veen1]

I do not know what is happening, but since this morning the token constantly expires. I notice this immediatly from a PowerAutomate Flow that runs every 5 minutes.

Earlier this morning, I already (successfully) refreshed using 'Switch Account'. However, an hour or so later, this happens again.

What's going on?

{

    "statusCode": 200,

    "headers": {

        "ETag": "W/\"e3-WGh1Z0qNbsWEoZFlRMbeqjQt8g8\"",

        "Vary": "Origin,Accept-Encoding,Authorization,X-Esri-Authorization",

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

        "X-Powered-By": "Express",

        "x-ms-environment-id": "default-19dea41c-63e9-4126-8596-ff22f8184216",

        "x-ms-tenant-id": "19dea41c-63e9-4126-8596-ff22f8184216",

        "x-ms-dlp-re": "UpdateItemInFeatureLayer|False|2026-06-08T18:56:46.5827633+00:00",

        "x-ms-dlp-gu": "-|-",

        "x-ms-dlp-ef": "-|-/-|-|-|-|-",

        "x-ms-mip-sl": "-|-|-|-",

        "x-ms-au-creator-id": "ca0a999e-5f7f-451a-a79d-585da7448c7b",

        "Timing-Allow-Origin": "*",

        "x-ms-apihub-cached-response": "true",

        "x-ms-apihub-obo": "false",

        "Date": "Tue, 09 Jun 2026 07:45:06 GMT",

        "Content-Length": "227",

        "Content-Type": "application/json; charset=utf-8"

    },

    "body": {

        "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

    }

}

[Erwinvan_Veen1]

This morning (our local time in Europe) I have been monitoring this issue. Roughly every 30 to 60 minutes the token seems to expire. The behaviour is the same as my previous comment.

I noticed sometimes the 'Switch account' option is available on the old ArcGIS Online connection and sometimes it isn't. Perhaps some work is currently being done which I am unable to see.

Currently, I am actively moving our flows away from PowerAutomate and rebuilding them in FME Flow. For a few instances this is problematic as not all activities are as easy in FME as they are in PowerAutomate, like sending attachments (of any supported file type) attached to an e-mail.

Presumably more Esri customers using PowerAutomate are active in the United States. I am curious to see any further comments to know whether or not this is an isolated incident.

[Erwinvan_Veen1]

Several hours later, this issue still persists. Every roughly 30 (not: 60) minutes the token expires.

Frankly, this is unmanagable. During working hours it's already nearly impossible to manually refresh the connection. Let alone outside working hours.

Although I am convinced there is will be a solution, I find the lack of support nothing less than shocking.  I'm not afraid to say this on a public forum.

Even though this might be temporary, this isn't the first time we've seen incidents like this. I am afraid this is the last straw and we see no other option than to move away from this connector and go to to a more robust solution.

[AkshayHarshe]

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

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

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

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

[AkshayHarshe]

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. 

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

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

 

[AkshayHarshe]

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]

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

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

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

[MichaelPierceVAIDSP]

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

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

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

[AkshayHarshe]

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.