Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
Thanks @Anonymous for the answers.
Unfortunately none of them worked in my case.
It got resolved on its own
Logic App Standard throwing Bad Request intermittently
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 98%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPS%3C/text%3E%3C/svg%3E)
Prateek Srivastava
0
Reputation points
We are experiencing some unusual behaviour in Logic App Standard since yesterday 16 Sep10:30 PM.
We are receiving Bad Request error messages on clicking Workflows blade.
Unable to view the workflow run history as well.
We have checked the App Service CPU analysis , memory usage and all seems to be fine.
Also tried to scale to WS2 plan from existing WS1 but didn’t seem to help.
Azure Logic Apps
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous2025-09-17T17:33:50.8233333+00:00 Hello Prateek Srivastava,
Thanks for reaching out on Microsoft Q&A and really appreciate your patience while we looked into this.
From the question:
- Logic App Standard is showing “Bad Request” errors intermittently when clicking the Workflows blade in Azure Portal.
- Workflow run history is not visible.
- Checked CPU, memory – appear fine.
- Scaling from WS1 to WS2 plan did not help.
Possible steps:
1.Storage account accessibility issues
- Logic App Standard stores workflow definitions, artifacts, run history etc. in a storage account. If that storage account becomes temporarily inaccessible (due to firewall rules, network issues, permissions, or intermittent service issues), then attempts to view workflows or run history may yield “Bad Request” or unable to fetch UI content.
2.Portal/UI service issues
- The portal might receive bad responses if backend host runtime (serving UI or metadata) is having transient errors. “Bad Request” from “Workflows” blade may come from communication with host runtime or metadata endpoints.
3.Plan / scale-out limitations
- Possibly the plan (WS1 / WS2) affects performance or resources; though OP said scaling from WS1 to WS2 did not help, there might still be intermittent capacity issues or service throttling.
References:
https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-diagnosing-failures?tabs=consumption
If you have further questions let us know and also please provide with requested information.
Thanks
-
Anonymous
2025-09-18T08:46:42.85+00:00 Hello Prateek Srivastava,
I hope the provided answer is helpful, do let me know if you have any further questions on this Please accept as Yes if the answer is helpful so that it can help others in the community.
Thanks
Sign in to comment