Hello,
We are currently migrating from the legacy Office 365 Connector webhook to the new Power Automate / Teams Workflow incoming webhook.
We created a new workflow from scratch to post messages to a Teams channel when a webhook request is received.
we are facing several issues:
1. 502 Bad Gateway on some calls
When triggering the webhook from our SAP system for some users, we receive a 502 error with an empty response body.
2. Run history shows only successful calls
In Power Automate run history:
- Successful calls appear normally
- Failed calls do NOT show up at all
→ This makes debugging very difficult
→ This also suggests that requests might not reach the workflow endpoint
3. Inconsistent behavior across users
With the exact same environment and configuration:
- User A can trigger the workflow successfully
- User B receives 502 Bad Gateway for the same request
4. What we have already checked
- Call reaches our outbound system correctly
- Successful calls are visible in run history
- We validated that destination retrieval and HTTP send are correct
- Tested also with tools such as Bruno/Postman → successful
Questions / Support requested
Could you please help us understand:
- Why failed webhook requests don’t appear in the workflow run history?
- What could cause a 502 error only for certain users with the same configuration?
- Is there a known issue related to authentication, trigger configuration, or Teams workflow permissions?
We would greatly appreciate any guidance.
Thank you in advance.
Share
Report
All responses (
Answers (
3,859
