Im scheduling the UiPath workflow from the cloud orchestrator, after starting the execution the job is added to the process in a folder right? there we can see the job execution status after the process is completed. how can we restart the same process if the execution status is faulted.
can anyone help me towards this?please.
Hi @Prabhakaran_Elango
your job should never reach a Faulted state, because once a job faults in Orchestrator, it means the automation has already stopped and cannot recover on its own. Faulted jobs break the execution flow, require manual restart, and make the automation unreliable in unattended scenarios.
To avoid this, a best practice is to handle all unexpected errors inside the workflow itself instead of depending on Orchestrator.
Please have a look on the below:
- Wrap your main workflow logic inside a Try/Catch
- In the Catch, handle the exception cleanly (logging, cleanup, notifications)
- Then restart your process through a controlled wrapper, not by directly invoking the same workflow inside Catch
@Prabhakaran_Elango
To restart the faulted job, navigate to the orchestrator folder where you job is faulted, then follow steps shown in below screenshot:
- Next, select user account & machine (if not auto populated) and click start
That’s it.
When you run a workflow in UiPath Cloud Orchestrator, a job is created under the process and you can see its status. If the job fails, you can’t restart it, but you can run a new job for the same process by going to Jobs, selecting the process, and starting it again. You can also set automatic retries so failed jobs try running again on their own.
@Prabhakaran_Elango
There is no automatic restart mechanism for this situation but you can build a workflow which uses orchestrator API’s to get faulted jobs within a timeframe you are desired.