Rest API calls made from prod process studio versus control room giving different results

a026833 — Tue, 01 Sep 2026 18:19:40 GMT

We have a process using the Utility HTTP VBO to make HTTPS POST calls to an external vendor using basic authentication. The process succeeds every time when run from the Process Studio on the Runtime Resource but fails (most times) when executed from the Control Room. The error returned on the control failures is a (502) Bad Gateway. What could be different between the 2 methods of running this? Using the same service account for both. I have seen it work from the control room after business hours but again inconsistently. Worked one night but then all failures the next. Fails consistently during business hours.System.Net.WebException: The remote server returned an error: (502) Bad Gateway at System.Net.HttpWebRequest.GetRequestStream()

Re: Rest API calls made from prod process studio versus control room giving different results

hossein.azimi — Tue, 15 Sep 2026 06:19:34 GMT

Hello a026833

Thank you for contacting Blue prism community.

Also thank you for providing the details. Although the same Blue Prism process and service account are being used, execution from Process Studio and Control Room may occur under different runtime conditions. Potential differences include the Windows session, proxy configuration, network route, environment variables, concurrent workload, and the specific Runtime Resource selected by Control Room.

The 502 Bad Gateway response indicates that the request reached a proxy, gateway, or load balancer, but that intermediary could not successfully communicate with the external vendor. As the issue occurs consistently during business hours but occasionally succeeds after hours, this may indicate proxy or gateway capacity, connection limits, request throttling, network congestion, or vendor-side availability rather than an authentication issue.

Could you please confirm and test the following?

●　Verify that both tests run on exactly the same Runtime Resource.
●　Confirm the Windows account and session used by Automate.exe.
●　Compare user-level, system-level, WinHTTP, and PAC-file proxy settings.
●　Run a small test process containing only the HTTP POST action.
●　Confirm whether other processes make concurrent calls to the same endpoint.
●　Record the exact timestamps of successful and failed requests.
●　Ask the network/proxy team to trace the failed requests at those timestamps.
●　Ask the vendor to check their gateway logs, rate limits, and connection limits.
●　Capture any correlation or request ID returned with the 502 response.

Since the exception occurs at HttpWebRequest.GetRequestStream(), the failure appears to occur while establishing or preparing the outbound HTTP request, before Blue Prism receives a normal application-level response from the vendor. Comparing proxy and gateway logs for a successful Process Studio execution and a failed Control Room execution should help identify where the behavior differs.

Regards
Hossein Azimi (APJ Team)

topic Re: Rest API calls made from prod process studio versus control room giving different results in Digital Exchange

Rest API calls made from prod process studio versus control room giving different results

Re: Rest API calls made from prod process studio versus control room giving different results