You’re offline. This is a read only version of the page.
2
Hi everyone,
I have isolated the behavior of a persistent 502 BadGateway error with the ServiceNow Connector, and it points to a session/caching bug in the connector itself.
The Setup:
Integration: Power Automate -> ServiceNow Connector.
Auth: Basic Authentication (Service Account, local user).
Environment: Enterprise (DNB).
The Issue:
The integration works initially but fails consistently after approximately a day with a 502 BadGateway.
The Workaround:
I confirmed that the credentials are valid and the connection object itself is not broken.
To fix the 502 error, I do not need to create a new connection or change the password.
I go to the Solution in Power Apps/Automate.
I open the Connection Reference used by the Flow.
I switch the connection to a different existing connection (e.g., "ServiceNow 25.01").
I immediately switch it back to the original connection ("ServiceNow 24.01").
Result: The Flow immediately starts working again.
Conclusion:
This manual toggle forces the Power Platform to refresh/re-hydrate the connection metadata. It seems the connector's session to the ServiceNow instance goes "stale" or gets corrupted, and the connector fails to automatically refresh the handshake, resulting in a 502.
Any help or similar experiences would be greatly appreciated!
Share
Report
All responses (
Answers (
