Hello Dima,
Unfortunately, I can’t recall for some out of the box solution here. Making the robot to wait for one hour is not acceptable.
I can suggest adding the additional task using an API call via PowerShell script.
API documentation attached.
You can add one hour pause in the PS script and start it directly from the wizard.
The other way to implement the delay is to start the PS script using windows Task Scheduler:
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/schtasks-create
Please let us know if you have any additional question on the matter.
Thank you.
hi,
I have unattented.
You offer when the robot performs a task and an error occurs, add a script to create a task in the task scheduler to start in an hour and make a .bat file to launch a specific wizard in an hour on the server?
I did such a scheme with a .bat file on PC user (anattended), I do not quite understand how it will work with unattended?
I like the api option better, if through it I can create a deferred task in the console and it starts in an hour, then it will be cool
Hi Dima,
The idea is, to add the task in the Console via API call from PS script in both scenarios.
The problem is that once added the task will start immediately.
I have proposed two different options to create the delay:
1. Add a one hour pause in the beginning of the API PS script. That way you can start the PS script directly from the wizard.
2. Create a task with specific time setting on the Task Scheduler. Here, the scheduler will launch the API PS script in the desired time.
Those scenarios should work on both attended and unattended setups.
Ok
why is there no parameter that allows you to specify the start time of the task when creating it through the api, if not specified, then the current time, if specified, then start after this time and you will not have to write any scripts and create tasks in the task scheduler
Hi Dima,
I agree, it will be convenient to have that, unfortunately, as I said, currently we don’t have an out of the box solution for your case scenario. I assume that this wasn’t implemented because the option to create a task at specific time is achieved via the Time Triggers. Once created, the task goes directly to the tasks queue and just wait there for a robot to pick it up.
hello, the option with creating a task in the Windows scheduler and running the file with the api access code works! thanks!
I will write a post as I did
to indicate the launch date, and not just the time, you must specify this