Get Asset: The response ended prematurely

[Kiran-Kishore (Kiran)]

One of my processes failed with this error:
Get Asset: The response ended prematurely

Any idea what this is about?

[SorenB]

Hello @Kiran-Kishore

Is it failing repeatedly or a one off error?
Perhaps check the Timeout property of the activity and debug via Studio.

Regards
Soren

[Parvathy (PS Parvathy)]

Hi @Kiran-Kishore

Check the below thread.

The Response Ended Prematurely Error While Opening Studio Or Assistant Connection

UiPath Studio/Assistant throws error "The response ended prematurely". Root Cause: While opening UiPath studio/ assistant, If it throws "Response Ended Prematurely" error then it could be due to network connectivity or proxy configuration which is affecting it's communication with Orchestrator. Resolution: Follow these steps to address the problem, Identify Proxy Presence: Analyze the system and identify the presence of a proxy configuration in the affected machine. Proxy can be checked in p…

Hope it helps!!

[prashant1603765 (Prashant Kumar)]

Hi @Kiran-Kishore

you can try increasing the timeout for the get asset activity . additionally, wrap the activity in a retry scope with up to 2 retries to handle any temporary connection issues or delays from orchestrator.

Happy Automation

[Jan_Brian_Despi]

Common Causes for “Get Asset: The response ended prematurely” in UiPath:

1. Network Connectivity/Proxy Issues: This is a very frequent culprit. The UiPath Robot needs a stable and unobstructed connection to UiPath Orchestrator to retrieve assets.

• Proxy Configuration: If your network uses a proxy server, it might be interfering with the communication. UiPath Robot and Assistant need to be correctly configured to work with a proxy.
• Firewall Rules: Firewalls (both local and network) can block the necessary ports or connections.
• Unstable Network: Intermittent network connectivity can cause the response to be cut off.

2. Orchestrator Performance/Load: If Orchestrator is under heavy load or experiencing performance issues, it might not be able to send the full response in time.
3. Asset Configuration/Permissions:

• Incorrect Asset Name/Path: Double-check that the asset name used in the “Get Asset” activity in your UiPath Studio workflow exactly matches the asset name in Orchestrator, including case sensitivity. Also, ensure the correct folder path is provided if you are using modern folders.
• Insufficient Permissions: The Robot user or the folder where the asset resides might not have the necessary “View” permissions for Assets in Orchestrator.

4. Timeout Settings:

• Activity Timeout: The “Get Asset” activity itself has a Timeout property. If the network or Orchestrator is slow, the default timeout (often 30 seconds) might be too short.
• Orchestrator Session Timeout: In some cases, prolonged inactivity might lead to a session timeout with Orchestrator, causing subsequent asset retrieval attempts to fail.

5. UiPath Version Mismatch/Package Issues:

• Studio/Robot/Orchestrator Compatibility: Incompatible versions of UiPath Studio, Robot, and Orchestrator can lead to unexpected behaviors, including communication failures.
• Activities Package Version: Sometimes, a specific version of the UiPath.System.Activities package (or other relevant packages) might have issues. Downgrading or upgrading the package version can resolve this.

6. Background Processes (for “Get Asset: The operation has timed out” which is closely related): If it’s a background process, ensure that the UIPATH_HEADLESS_WITH_USER system environment variable is set to True on the robot machine. Background processes run in a different session context, and this setting can be crucial for asset retrieval.