Solved: Re: Getting "Unauthorised" message

Anonymous · ‎05-01-2019

Hi all,

My flows have been working fine up until today, where I have been getting this error message "Unauthorised" when updating Sharepoint list. Has anyone else come across the same issue? The account that is triggering the flow has permissions to update the sharepoint list

v-bacao-msft · ‎05-02-2019

Hi All,

MS Flow Support has released an update and this issue seems to have been resolved.

https://preview.flow.microsoft.com/en-us/support/

Please check if there is still an issue with the related Flow. If so, please let us know.

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

AronBrown · ‎05-01-2019

Morning Starship12, I am having the same issue. Tried to re-run several times today and I am continuing to het the error on sharepoint list steps... Is this a known issue?

martinav · ‎05-01-2019

Same here. MOST flows are failing on simple SP Get Items and such actions. This is a DOWN situation! Microsoft ticket is submitted.

AronBrown · ‎05-01-2019

Do you have a ticket # for anyone to keep an eye on?

martinav · ‎05-01-2019

You have a way to do that?

SR number 119043023002044

For your info, I had them on the phone yesterday, and they did see the errors ocurring. After about 30min of trying different things, the flows started working again. When I asked "what did we do, and why are they working again?" they were not able to asnwer. That concerned me most, because I'm not sure they even understand what is happening yet. Also, the lack of a message on https://powerapps.microsoft.com/en-us/support/ does not give me much confidence that we are anywhere close to a solution yet.

AronBrown · ‎05-01-2019

Not on the site, but if you call in referencing a ticket #, they escalate after it gets so many responses

martinav · ‎05-01-2019

Ok, good. I posted this on another post in the PA forum.

AronBrown · ‎05-01-2019

Hi Everyone,

Wanted to follow up with you all, I just got off the phone with Microsoft Flow Support team and they let me know it is a known issue and took time to review my flow that was erroring out with this error as well to make sure it wasnt something else.

They let me know the ETA on its resolution is 2-3 days unfortunatley... But hey, at least its not our flows that are the problem. I was for sure my flow had become unstable due to a change with the new monthly updates.

Thanks everyone! - Aron Brown

martinav · ‎05-01-2019

@AronBrown

I wish it were our flows... and we could make a change the problem never happens again! Issues like this are core to the system. I have been experiencing down time about once a month from core problems like this, and if this continues, I think my company will be ending it's use of these tools. The features are great, and the interface for the users is great, but core reliability is somthing we cannot sacrifice. I'm very concerned that these tools are mature enough to rely on in a business environment. Down time means we have idle people, and that is far too expensive to accept.

AronBrown · ‎05-01-2019

@martinav

Agreed, But for me its riding a fine line of how fast this platform is scaling and the ability to edit in JSON. With how fast it is growing out, i expect issues to arrise. But for me, I cant sell this to my clients if it is unstable and causes re-work by analysts. so I am split on this issue to be honest

martinav · ‎05-01-2019

So far, I have seen three types of problems. These are problems that come up AFTER you have your app working, and all of the suddon, something happens.

1. Issues that require you to rewrite things because what worked once, no longer does. (example, using Gallery.Selected as your "Item" in an edit form quit working properly. Now, use Set(GalleryItem,Gallery.Selected) then use GalleryItem as your item, because forms started pulling in the WRONG data if you didnt do this.

2. Issues like today. Core issue makes your apps stop working for some or all users... some or all apps.

3. Uncertainty with App Advanced Settings. The descriptions on these settings make them sound like they will help you, or encourage you to use them. Unpredictable results with settings one way or another make it very difficult to know where these settings need to be. Even calling MS for help... I have had them say "Try changing <Setting> off it it is on, or on if it is off." This does not give me confidence that even MS knows how these settings will affect your apps. These settings need to be well defined, and it needs to be understood what functionality may NOT work with any of them set one way or another. There are FAR to many of these settings to practically turn them on and off as trial an error to see what they do. This is a big issue.

v-bacao-msft · ‎05-01-2019

Hi @Anonymous @Anonymous @AronBrown ,

MS Flow support has also released relevant information to confirm some flows using SharePoint Online connector started failing with the "Unauthorized" error code.

Please check this link:

https://preview.flow.microsoft.com/en-us/support/

This issue is currently being fixed, if there are any updates, we would post back in time.

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Anonymous · ‎05-01-2019

Hey Microsoft Flow Team, I have this issue too and it drove me crazy trying to figure out if I had accidentally changed any permissions. I have a few flows that all seem to fail with "Unauthorised" message during Create item or Update item in list. How do I submit a ticket # to escalate this issue? Please resolve it asap and let all of us know when it's resolved. Thanks!

Anonymous · ‎05-02-2019

Hi @Anonymous , you can log tickets with Microsoft from this website https://emea.flow.microsoft.com/en-us/support/ , scroll down and click on "Contact Support". I think you can call to report as well but I'm not sure what their number is

bulbulm · ‎05-02-2019

Hi All,

I am stil seeing this intermittent issue. Also I have raised Sev A case but till now no update from them. Is this issue still persists in yours Teneant.

bulbulm · ‎05-02-2019

Hi All,

Just now I had a call with MS engineer and issue has reolved 10 minutes back and I am able to create flow.

As this issue is intermittent only so keep observing.

v-bacao-msft · ‎05-02-2019

Hi All,

MS Flow Support has released an update and this issue seems to have been resolved.

https://preview.flow.microsoft.com/en-us/support/

Please check if there is still an issue with the related Flow. If so, please let us know.

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

ThomFromUoC · ‎05-15-2019

Hi Kris

Any chance you could provide a direct link to where the release notes are fo rthis issue? They provide a more official resource to our users to explain the issues we've had.

Many thanks

Thom

martinav · ‎05-15-2019

@ThomFromUoC

This is a good question. Haveing a log of the history would be a nice reference.

@v-bacao-msft I have seen excerpts of such a history. Is this publically available?

DataFailure · ‎07-19-2019

I have encountered this error on some runs in 3 of 8 of my flows on the 12th and 15th of July. Has anyone else encountered this error on those days or in the last week?

Is there anything I can do other than resubmit the runs that failed?