Power Platform Community Forum Thread Details

increasingly sporadic "bad gateway" on HTTP post in a parent/child flow

Hey there,

I have a system that uses a parent flow and a child flow. The parent flow makes an HTTP post call that then triggers the child flow that is configured with a "when an HTTP request is received flow".

This process worked almost perfectly for a while and then for a few months, was about 95% reliable and is now trending down to the 80% reliability mark.

The parent flow sometimes errors out with a "bad gateway" with the error body being:

{
  "error": {
    "code": "NoResponse",
    "message": "The server did not receive a response from an upstream server. Request tracking id '(censored)'."
  }
}

One person can get this error and another person, minutes later, will not get this error.

What is very strange is that if a person has this error, then another person does not have this error, when I resubmit the flow, it will error out as well.

This parent/child flow system works for most people, but seems to be getting less reliable as time goes on.

The reason I have it configured this way is that I have a sharepoint site that uses a word document library that I want people to contribute to, however I do not want a user to see another user's word document in this same library.

The parent flow makes the word document as a service account, then makes an HTTP post with some information about the end user (Gathered from powerapps).

The child flow will then grant permission to the powerapps user to edit the word document and makes some logs for me as an admin.

I am trying to avoid having to manually grant permissions on this system because it is not sustainable for me to do this task in addition to my other workload.

Any advice is appreciated. 

Thanks