Office 365 Group Action failing "Unauthorized" - URGENT

[martinav]

I am having Office 365 Group action problems.  I have had several otherwise good flows fail today with unauthorized error in my List group members action.

Is this the same issue we had last week with the same error on Sharepoint actions??

[Brad_Groux]

This is likely because you are using the wrong account on the step, and/or you need to re-authenticate your connection credentials. Browse the Data > Connections:

Then select the connection that you'd like to refresh, and you can do so be deleting the connector and re-adding it (Office 365 in this case), or by selecting the Switch account option:

Also, you can make sure that the proper account is listed under the My connections settings of the step:

If that doesn't fix the issue, if you provide us a detailed view of the error(s) we may be able to assist further. 

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[martinav]

@Brad_Groux ,

Yessir, those are the first things to check.  All connections are good.

1. These flows have been working for months.  Thus, correct connection selected.

2. Other flows using the same connection are not having the problem.  I simply do not have the time to delete the connection, and re-add it.  If it is working in other flows, I dont presently see how this would help.  Its not that I'm lazy, but I just counte 31 flows with this connection.  Literally, I do not have the time to delete it and reconnect it as a trial and error.  Also, because it is working in other flows.  I have to consider it to be a MS issue.  Especially since SP had the exact same random error, which was attributed to a "throttling error" that was a MS problem.  See 

https://powerusers.microsoft.com/t5/Connecting-To-Data/Microsoft-Flow-SharePoint-Connection-Unauthor...

@Mr-Dang-MSFT , can you confirm that this is related or not?

Thank you.

[Brad_Groux]

Deleting and re-adding a connection doesn't require changing anything within your Flows. The reply given was provided based upon the information provided and common resolutions.

You could certianly be hitting thresholds of Flow in the Apply to each loop, but there is no way for us to know that without having a detailed and expanded screenshot of the steps. You could be looping two times, or two thousand times, we can't see and thus don't know.

The Flow documentation for each connector outlines the limitations (if any) of every connector, including Office 365 Groups, which has serious Throttling Limitations. If you're hitting these thresholds, you can add a delay to your Flow. 

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[martinav]

This is not a solution, but one of the flows that errored yesterday worked fine today.  I will keep updating this thread as the day goes on.  It appears a similar case as the SP issue last week.  Random authroization errors with no apperent reason.

[martinav]

@Brad_Groux ,

Thanks for your reply.  My initial post was more of a fishing expedition to see if others were getting the same errors, similar to last week.  I was not looking for a solution beyond that when I posted it.  I have found that if there is an issue with MS, getting a few users to pile on first gets the ball rolling much quicker.  

I had other flows fail yesterday, and the one I post here is as simple as it gets.  Two single calls to SP, no looping, then a list group (the failed action) which contains a single user, then an email send.  There is no way this is a limit issue.  

[v-yamao-msft]

Hi @martinav ,

Thanks for sharing and updating.

It seems that it is working properly for you now.

Best regards,

Mabel

[martinav]

@v-yamao-msft ,

Mabel,

I'm not sure how to respond to that.  While it may have worked in two occasions yesterday, I have no understanding why those actions failed previously.  I NEED to know why these things are happening in order to know how to prevent it from occurring again.  Without the understanding of what is happening, eliminating the problem is not possible.  This is a massive problem.  EVERY time a flow fails, or there is some unexplained error in PA, I have to do a FULL investigation of the data that was being operated on, to ensure it is correct across FIVE systems!  At this point in time, I am the ONLY one in my organization that can do this, and I am afraid there will never be another person with enough background in PA/Flow, and my apps that can perform these checks.  Thus, I am married to this system, with no way out of it.  

These apps and the underlying system (MS Cloud apps) MUST improve in their reliability or the efforts I have placed in making these apps is for not, and my apps will eventually be eliminated.  Either from the cost (time) to keep them going, or I find another job and no one can pick up where I left off.

This is the weakness of these apps.  There must be an improvement in reliability BEFORE there are more features and functionality improvements made.  That is where I implore MS to change their directives to focus on quality.

I cannot mark this thread complete with just one day of success.  The underlying problem of reliability remains open.

[martinav]

@v-yamao-msft ,

I have confirmed today that this is still broken!  I cannot signoff anything until this is fixed.  This List Group action is failing.  The connection is fine.  THis connection is used in 5 other flows, and it is working in thise just fine.  

These are the steps I have taken.

• I have reordered the flow to isolate the action.  I have deleted and re-created the action. - Still fails
• If I test the flow, and I select the trigger action, it will pass.  But, when I trigger the flow from Powerapps, or if I "resubmit" a failed flow, it fails.  See screen shots.

This is what I get when I run the flow as designed:

If I trigger the flow manually, it works:

This is a 100% problem.

[v-yamao-msft]

Hi @martinav ,

I have just tried to reproduce this issue, however, it is working properly on my side.

It is working successfully when I trigger the flow from PowerApps.

Have you made any changes on the flow then test it with previous runs? Sometimes an error will occur if you made changes to the flow then test it with previous runs.

Best regards,

Mabel

[martinav · Accepted solution]

@v-yamao-msft ,

I would not have expected it not to work for you.  I had mentioned this action was working in many other flows.  

I did end up getting it to work.  It is very troubling to me on why I had to do this...  The resolution in this occasion was to remove the flow from PA, and then add it back again.  

This is another example of how I am not sure that I will be able to continue using PA and Flow as a solution for our needs.  There is nothing logical about why this stopped working, other than perhaps some random fallout from the throttling errors that we had about two weeks ago that gave similar errors.  This flow had been working error free for many weeks. 

There is no one else in our organization that has the background to fix these apps.  This is not something I can get working, and then forget about and do other things.  We have apps that were developed in .net that were that way.  The developer made the app about 4-5 years ago, then he left the company but it has been working without any need to "fix" it.  It just works.

This is not a situation that we can afford to sustain.  Troublshooting like this is completely trial and error, and there is nothing that can be done to avoid such problems, as they just happen from nothing.  My only saving grace is that I only have 5 or so users that use these apps.  I truly would not have time to do ANYTHING but fix these apps if I had a user base of even 10 to 15 users.  At that point, trying to keep this system working would be all I did.

I mark this as my solution.  Even though, it is not really a solution at all.  I just got lucky and did something that cleared the issue.