Asset Loading Issue

Team,
Im geting error this often , not sure why there is asset , no changes in setup..
Could anyone please let me know if you had experienced the same or know the reason for this error.
Much appreciated.

Loading asset <AssetName> failed: Bad Gateway (502) means Robot failed to fetch an Orchestrator Asset due to backend / connectivity issue.

Since you already verified Asset is present and no changes,

  1. Ensure Robot–Orchestrator connectivity.
  2. Add retry logic with delay
  3. Avoid repeated asset calls inside transaction loops.
4 Likes

Hi @mysoftlabs

This is a transient Orchestrator connectivity issue.502 Bad Gateway occurs when the Robot cannot get a valid response from Orchestrator while loading the asset.
Solution ~ add retry logic around Get Asset and verify network stability.

Hope it help to resolved your issue

Thanks & Happy Automations

The asset itself is not the problem, especially since no configuration changes were made and retries succeed.

Hi @mysoftlabs ,

Try this

  • Retry usually works

  • Check Orchestrator service health / status

  • Verify network stability, proxy, and firewall rules

  • Add retry logic around Get Asset

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.