I get a Bad Gateway error when my flow tries to connect to DevOps. I already have a flow working fine when connecting to my Azure SQL database, but can't get any joy with connecting to DevOps. Can anyone help please?
I am experiencing the same problem with a flow connector triggered by Azure DevOps.
Hello,
I have a smilar problem. The connection to Azure DevOps from Flow is established correctly, however when I try to use the connector in a (newly created or old) flow it gives me the following error: https://paste.pics/6OB7X . I tried deleting the collection and recreate it, deleting cookies and using incognito mode of my browser. All have the same result.
Here is a screenshot from the connector: https://paste.pics/6OBAY
Would be awesome if anyone could help me out! For instance, can the 'clientRequestId' in the error message be used to trace what is going wrong in your backend? Thanks a ton!
Warm regards,
Doris
Images now uploaded. The "Photos" option took me to a completely different UI last time I clicked it ! Very strange! This time it took me to a familiary upload UI 🙂
I don't know how to upload a screenshot to this forum. Even "Photos" isn't very intuitive. Anyway, you're right. I don't get an error when I created the connection. Only when I run the flow. My other flows are working ok with my Office 365 stuff. And I thought Gateways were only for on-premise connections? I'm probably wrong ! My DevOps is Azure DevOps.
{
"error": {
"code": 502,
"source": "uk-001.azure-apim.net",
"clientRequestId": "8b6bbea3-4cd2-43d1-9b34-a4cdd4d82453",
"message": "BadGateway",
"innerError": {
"status": 502,
"message": "An error occurred while sending the request.\r\nclientRequestId: 8b6bbea3-4cd2-43d1-9b34-a4cdd4d82453",
"source": "vsts-uks.azconn-uks-01.p.azurewebsites.net"
}
}
}
Hi @Advent7 ,
Could you share more details of the error message and a screenshot of the Flow configuration?
As far as I know, this kind of error occurs when Flow is executed. It seems that there is no such error when configuring the connection.
Please try to recreate the connection, or clear the browser's cache and reconfigure the connection/Flow.
Best Regards,
Michael E. Gernaey
566
Super User 2025 Season 1
David_MA
516
Super User 2025 Season 1
stampcoin
492