I have built a robot that runs a process successfully, and because the result is not visible before the next day I am using the “Resume after delay”-activity (part of UiPath.Persistence.Activitites) to continue the job when the system have made necessary changes to be able to continue.
I have successfully tested this functionality on a different robot with a delay of 5 minutes, but when I use it on this robot and set the delay to +1 day the job got cancelled after approximately 12 hours without any trace in the logs. Last info in the log is the expected “ececution suspended”-message and nothing that could explain the cancellation.
This happened early this morning, and I was expecting it to still be suspended when I checked.
Can anyone explain this behaviour?
Is this caused by the Orchestrator (community license is used during developing), or are there a max delay on this functionality before all suspended jobs are cancelled?