'Keyset does not exist' error

[SebastianMusiol]

Hello,

Recently in one of my flow I got an error which didn't appear previously (when flow tries to find a record in Dataverse).

Http request failed as there is an error with the authentication credentials provided: 'Keyset does not exist
'.

Few details:

- trigger is an HTTP request (no params in json)

- Degree of Parallelism is set to 1 for flow/trigger

- flow is executed every day circa about 60 times

- Flow is processing somedata

- After all 'Apply to each' step updates Dataverse table (Degree of Parallelism is set to max/50, only  2x60 records to be found and then to be updated or created during each flow execution, so small table)

- And here I'm receiving mentioned error (when I'm trying to find a record) from time to time (not for each flow execution) and only for 1, sometimes 2 records (not for each iteration in 'Apply to each' step to be precise).

- in the last week error happened 6 times for 2 different tables

- this issue I observe since last month maybe.

Do you know anything about this error? How to solve it?

Just to highligh that this particular flow is a business critical one so that is why I want to find a solution...

[v-mabalagan]

@SebastianMusiol

[SebastianMusiol]

Hi.

No, nothing new.

All I did was to implement workaround - repeat previous/failed step.

Additionally I started to track how often this issue happens -> 6-8 times a week.

Last failed was yesterday.

Any clue what it might be?

[Anonymous]

Up !

Have same issue here! any solution? thanks

[daxjkent]

I'm getting this error as well with pretty much the exact same conditions as original poster.  Any updates or solutions?

[SebastianMusiol]

@Anonymous , @daxjkent unfortunately nothing from my side.

What is interesting, last time when I saw this in my flow was 4 times on 2021-12-30, since that time works perfectly - I did not change anything.

All I can propose is to add step which is executed when previous / affected step fails, and this new step can just repeat failed action (with some delay) + mail for tracking purpose.

[daxjkent]

Thanks for the info. Unfortunately it's not happening in any one single place but randomly thru our hundreds of flows.  We have a priority ticket in with Microsoft.

[SebastianMusiol]

Okay, so it is more painful...

Anyway, let me know if you get any root cause and / or solution from MS.

[Anonymous]

I have no more problems from my side. 

Let me share with you the currect incident from MS

https://portal.office.com/adminportal/home?#/servicehealth/incidents

Title: Users are intermittently unable to view gateway connection lists
within the Maker Portal and Flow Portal

User Impact: Users are intermittently unable to view gateway connection
lists within the Maker Portal and Flow Portal.

Scope of impact: Some admins are also unable to sign into the Connectors
Root cause: A code issue is causing a "null" response to be provided
while the service is making the User Principal Name (UPN) claim,
resulting in impact.

Start time: Wednesday, July 27, 2022, 2:00 PM (12:00 PM UTC)

[drypz]

This issue has been prevalent in the past few days. Some of our flows has been affected by this and we are cluecless why this is happening. We tried to recreate one of the flows but after several runs, the issue come out again and again. Microsoft should fix this ASAP, a lot of developer hours has been wasted because of this.