Unanswered

Which is the correct error?

(0) Share

Report

Posted on by buildbod

130

I have a Flow that has started randomly failing. It worked fine for many hours and then started crashing. It crashes at the same step (so at least that is consistent). However the error codes are not.

The Flow is called from a PowerApp which reports a 502 error.

Inspecting the Flow yields a 400 error.

Which one is right? I'm suspecting the 502 error as I know the Flow has run successfully many times.

I'm also at a loss at how to defend against this fault. I cannot expect users to wait an indeterminate period of time for the 502 to clear.

In PowerApp In Flow In Flow

Categories:

Using flows

I have the same question (0)

All responses (2)

Answers (0)

v-yuazh-msft on at

Like (0)

Report

Hi @buildbod,

Does your problem still exists?

Could you please share a screenshot of the configuration of your apps and the flow so we would try to provide a proper workaround for you?

Best regards,

Alice

Was this reply helpful? Yes No
buildbod 130 on at

Like (0)

Report

Yes it still exists but I think I've worked out what is happening. I downgraded my permissions on the SharePoint site from Site Collection Adminstrator to Contribute to finalise some tests. I had been testing the app many, many times with my elevated account.

I am issuing a SharePoint HTTP request to 'Break inheritance'. The person running the Flow only has contribute rights and so the action is failing due to insufficient permissions. I have rewritten my Flow now to include SharePoint App that has FullControl permission and then replaced the SharePoint HTTP action with a HTTP-HTTP action that includes an Authorization token from the App. This works fine.

I tried adding the Authorization token to the SharePoint HTTP action but that failed. I think it failed as SharePoint was seeing two tokens: one hidden in the Flow action that carries the token of the user executing the Flow and my additional one.

What is confusing is the variation in error messages. Calling the Flow from PowerApps generates one message. Inspecting the Flow another. Neither are correct.

Original actionRevised action

Was this reply helpful? Yes No