The operation has timed out - Orchestrator

Feedback Orchestrator
,
1

Bots are failing while get asset details from orchestrator. Error message:

System.TimeoutException: The operation has timed out. 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)

3

Hie @Elancheran_E18 use your activity inside the retry scope and increase their number of retry and interval time…
cheers

4

we are facing this issue in multiple bots. Previously bot was running fine. Last two days, we are facing this issue. Is it related to robot machine issue or orchestrator connection issue?

5

Hi @Elancheran_E18

1 . Try to use modern activity
2 . Increase the timeout value in Get Credential activity and check

Hope it helps you .

6

@Elancheran_E18 no i don’t think its because of robo or orchestrator … Just try with one project and use retry mechanism because we can say it only for a Secure Purpose some time the server is slow down so that scenario that retry mechanism comes in the picture to help …
here are some tips you can follow :

  • Increase Timeout Settings:
  • Activity Timeout: If you are using activities with timeout properties, try increasing the timeout duration. For instance, if you’re using an Get Asset activity, check its properties and increase the Timeout value.
  • Orchestrator Timeout Settings: Check Orchestrator settings for any timeout configurations that might be affecting the request.
  • Check Network Connectivity:
  • Ensure that the machine running the bot has a stable network connection to the Orchestrator.
  • Verify that there are no network issues or firewall rules blocking communication between the bot and Orchestrator.
  • Orchestrator Performance:
  • Ensure that the Orchestrator is not experiencing performance issues or high load. Sometimes, if Orchestrator is under heavy load, responses can be delayed.
  • Check Orchestrator logs for any performance-related issues or errors.
  • Asset Availability:
  • Verify that the asset you are trying to retrieve exists and is correctly configured in Orchestrator.
  • Ensure there are no issues with the asset itself, such as incorrect permissions or missing data.
  • UiPath Studio and Orchestrator Versions:
  • Ensure that you are using compatible versions of UiPath Studio and Orchestrator. Sometimes, version mismatches can lead to unexpected issues.
  • Check for any updates or patches for UiPath Studio and Orchestrator that might address known issues.
  • Retry Mechanism:
  • Implement a retry mechanism in your workflow to handle transient issues. For instance, you can use a Retry Scope activity to retry the operation a few times before failing.
  • Logs and Debugging:
  • Check the UiPath logs for any additional details about the error. Look at both the Orchestrator logs and the logs from the bot machine.
  • Enable detailed logging in UiPath Studio to capture more information about the error.
    cheers