web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Automate
Unanswered

Bad Gateway

(3) ShareShare
ReportReport
Posted on by Microsoft Employee

Flows were working up until 19 hours ago, no flows have run since then, I now get a bad gateway error, with the following: -

 

{
 "error": {
 "code": 502,
 "source": "europe-001.azure-apim.net",
 "clientRequestId": "dbf49874-bd41-4c76-9727-8288d6edace5",
 "message": "BadGateway",
 "innerError": {
 "status": 500,
 "message": "Value does not fall within the expected range.\r\nclientRequestId: dbf49874-bd41-4c76-9727-8288d6edace5\r\nserviceRequestId: 9b68839e-7081-6000-3f28-e457108e5d25"
 }
 }
}
 

I have tried deleting the connectors for both Sharepoint and Outlook and recreating them but no success.

 

On test the flow fails immediately.

 

Bizarrely these failed runs do not show in the run history

image.png

Categories:
I have the same question (0)
  • v-yamao-msft Profile Picture
    Microsoft Employee on at

    Hi @Anonymous,

     

    How is your flow created? Could you share a screenshot on your flow?

     

    Are you now still having the issue on your side?

     

    You said that the failed runs don’t show in the run history, could you check them by clicking See all?

     

    I created a simple flow to send an email when a SharePoint item is added in a list, it worked fine and didn’t return any error message.

     

    Error 502 means the failure is temporary or transient, please try to resubmit to try the flow again.

     

    If you are still having the issue, please feel free post back. 

     

     

     

    Best regards,

    Mabel Mao

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    Hi Mabel,

     

    Please find attached 3 images: -

     

    1) Top section of flow

    2) Overview of entire flow

    3) Error

     

    112233

    Yes the issue still exists, no change at all.

     

    Yes I did that, last run in the history is dated 9th August.

     

    Well thats good, but as I said the flow was working for days with no problems and then it stopped, no changes were made it just stopped working.

     

    I wouldnt say a failure that has now been occuring for over 3 days is temporary or transient, you are just telling me what it says in the troubleshooting guide, could you explain exactly how to resubmit, as there is no resubmit button, maybe share a screenshot? If you mean edit and save the flow I have probably done this around 100+ times, not very temporary or transient eh???

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    Also for your information I have just created a new flow that simply sends an email when an item is created or modified and this also fails...

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    Again for your information, if I change the List Name to a different list the flow does not fail, If I change it back the flow fails immediately with the Bad Gateway error...

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    Any Update??

  • grahampasmurf Profile Picture
    133 on at

    I have the same issue, same error message.  BadGateway or Bad Gateway

     

    It happens in the SharePoint Get item action.  My flow was working fine for many days until it simply stopped working about a week ago.  I tested using new flows and new lists and the same issue occurs.

     

    More details:

     

    “error”: {
    “code”: 502,
    “source”: “flow-apim-msmanaged-na-centralus-01.azure-apim.net”,
    “clientRequestId”: “7efe60db-ed54-428a-b79c-201bbb8fb2a8”,
    “message”: “BadGateway”,
    “innerError”: {
    “status”: 500,
    “message”: “Value does not fall within the expected range.\r\nclientRequestId: 7efe60db-ed54-428a-b79c-201bbb8fb2a8\r\nserviceRequestId: 01b7849e-00ca-6000-4972-d018cc4386ac”

    Also, in my “Get item” action I double-checked the list name & location is correct, the Id is simply 1, and it makes no difference if I select "All Items" view or “Limit Columns by View.”

     

    I am going to assume this is a Microsoft bug that was introduced a week ago.  I will wait for it to be fixed, but I already developed a workaround.  I simply hard-coded in the data that I want, instead of calling it from a list.  Makes the flow less flexible but it still works.

     

    Also, I learned something useful, and that is to use the "Configure run after" setting to allow my flow to continue even after the error.  I put my "Get item" and "Set variable" into a Scope box.  If anything in that Scope fails, the next action is configured to run regardless.  And the variable already had a default value.  Also make sure not to run your Set Variable if the Get Item fails.  Maybe this tip will help someone else out there.

  • stschilar Profile Picture
    13 on at

    I am also having the same issue.  Bad Gateway error on my Sharepoint "when a new item is created" flow since yesterday 8/14.

    When a new item is created, it does not show in the run history.

     

    I tried rebuilding the flow, but that did not solve the issue.

  • EdgarB Profile Picture
    3 on at

    I am having the exact issue. One of our Get Items step is limiting the columns by View because it has "too many lookup columns" so this completely broke my flow.

    Care you elavorate in how you got it working? I am new to Flow and Sharepoint and I am in a deadline to get this corrected ASAP so I cant exactly wait for Microsoft to fix the bug.  

    Its a simple command to just get all the items in the list and export the list via HTTP to another Flow to make an addition to a column. Here is what it looks like but since Sunday this week it stopped working.

    2018-08-15 15_32_47-Edit your flow _ Microsoft Flow.png

     

    Any help is appreciate it. 

    Thank you! 

    ~Edgar

     

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    Hi,

     

    I am also experincing the same issue with a FLOW on an Update Item action. The flow ran successfully 2 weeks ago.

    My runs do however detail the failed attempt in the history list though.

     

    Has anyone logged a support call or received feedback on the issue?

     

    Thanks,
    Angela

  • stschilar Profile Picture
    13 on at

    I have my IT Ops director submitting a ticket on my behalf today.  I will let you know if I find anything out!  

     

    Sometimes it is nice to know I am not the only one having issues!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 248 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 204

#3
Haque Profile Picture

Haque 179

Last 30 days Overall leaderboard