When a job fails after successfully completing some steps (e.g., steps one and two), how can you resume execution from the point of failure (e.g., step three) without restarting from the beginning? This allows bypassing completed steps and resuming from a designated intermediate point.
Hey @AutoBot_Edge
The most common approach is to use a checkpoint mechanism, where the process saves its current progress (e.g. to a file, Orchestrator queue item, or Asset). After each major step (Step 1, Step 2…), you store a marker of completion.
When the process restarts, it reads that marker and jumps to the appropriate next step.
You can implement this via a Switch or Flowchart, where each step is a separate block.
It’s a manual strategy, but gives you precise control over where to resume execution.
1 Like
Hey @AutoBot_Edge ,
Resuming Execution from Failure Point in UiPath
To restart from the point of failure without repeating completed steps, use these methods:
Use State Machine (Best for REFramework)
Store progress in a transactional state (e.g., Step 1, Step 2).
On failure, restart from the last successful state instead of from the beginning.
Implement Checkpoints (Best for Linear Workflows)
Store the last completed step in a file, database, or Orchestrator asset.
On restart, read the last step and resume execution from there.
Example:
Step 1 Done? → Skip if yes
Step 2: Done? → Skip if yes. Start from Step 3
Use Queue Transactions (Best for Large Processes)
Break the process into queue items (e.g., Step 1, Step 2, Step 3).
If a failure occurs, the bot picks up from the next pending queue item.
Try ContinueOnError & Retry Scope (For Small Failures)
Use Try-Catch to handle minor failures without stopping the job.
Please let me know is it work or not
1 Like
Welcome to UiPath,
you can track progress using a variable like “StepToResume” to indicate the last successful step. After each step, update this variable and use conditional logic to check its value, allowing you to skip already completed steps
If you found helpful, feel free to tick as a solution.
Happy Automation
1 Like
You need one place to store your current step. Design should be modified accordingly
If you want this feature in Performer - I would suggest you to create a transaction item property to store next step and update it after the completion of each step
Other option would be to use a database. If applicable - let me know so that i can explain in details
Now coming to process.xaml - First step is to identify the next step and the output should go to a swicth flow chart and distribute accordingly. Each step action should be a sequence in the process.xaml file
It should look something similar. Process.XAML
1 Like
You can use Set Transaction Progress activity after each steps i.e., step1, step2 and step3
Use if activity before sequence(i.e., Step1, Step2 and Step3) and check
In_TransactionItem.Progress.Equals("Step1 Done")
If yes, Step1 is completed. like that do for all steps
Regards,
1 Like
Its worth paying attention to Maestro, if you design your process high level in Maestro you’ll be able to resume from a point of value, aswell as being able to manipulate variables in memory aswell.
Its going to be a great way to try to resume from a failure.
1 Like
Thank you, it worked.
1 Like
Hello @sharazkm32
I am a beginner at UiPath and currently not very familiar with the concepts of transactions and queues. I hope you can share this XAML file with me as I would like to further my learning. Thank you