System.Exception: Invalid Request!

News Knowledge Base
1

The following error message is observed in the Orchestrator several times a day for different processes: Info: Invalid request! If the processes are re-started manually, they run without errors. The credentials to the database are used(Provider Name / Secure connection String) as a "shared asset" in the Orchestrator.

Issue Description:

The error message "System.Exception: Invalid request!" might be related to an issue with the asset retrieval process from Orchestrator.


Error Message:

Info: Invalid request!

System.Exception: Invalid request! at UiPath.Core.Activities.BaseAssetActivity.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)

at System.Activities.AsyncCodeActivity.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext context, IAsyncResult result)

at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager



Root Cause: The root cause of the issue could be one or more of the following factors,

  • Network latency between the Robot and Orchestrator might lead to connection delays, causing difficulties when fetching assets
  • Orchestrator might be experiencing high loads during specific times, leading to slower response times when assets are being requested
  • It is possible that there could be an issue with how the assets are being retrieved within the workflow, causing the "Invalid request" error.

Resolution: To address this issue, consider the following approaches with respect to the causes mentioned above,

  • Investigate and monitor network performance between the Robot and Orchestrator to identify any potential latency issues.
  • Monitor Orchestrator performance during peak times to ensure it's operating optimally and is not overloaded.
  • Add a Retry Scope around the Get Asset Activity (Read more on Retry Scope). Also increase the Timeout MS property of the mentioned activities. By Default the Timeout MS is 30, so add 30 more which would be 60 (Activities - Retry Scope Activity ).