Scheduler
Last updated
Last updated
IMPORTANT:
When you use Scheduler for the first time, you need to log in to your agent (see instructions here: Log in to the Agent).
During the scheduled time, your agent must be active. That means if you quit it or restarted your computer after which you didn't activate the agent, the scheduled task won't happen because there is no agent to run it.
During the scheduled time, your computer must be turned on and active. You may want to adjust your sleep mode and battery settings to ensure that your computer doesn't turn off or switch to a sleep mode for the time that the TaskBot is scheduled to run.
Click on the scheduler icon inside your TaskBot, as shown here:
A dialog will open. Now you choose the time or interval for your TaskBot ton run.
Yes, you can run parallel scheduled jobs - just make sure your computer has enough capacity to handle multiple parallel executions.
Let's say, you have a dedicated computer A where you want to run your scheduled TaskBots, and you have computer B where you want to continue building and running TaskBots (in this case running means that you manually click on the run button).
To enable this setup, follow these simple steps:
Install the agent on both computers A and B.
Log in to your scheduler inside the agent on your computer A (as described here: Log in to the Agent).
Do not log in inside the agent on your computer B.
Explanation: Your agent needs to be logged in only for scheduled runs and runs triggered by webhooks (Trigger Run via Webhook). It does not need to be logged in for runs that happen when you click on Run button manually. So by logging in only to the agent that runs scheduled TaskBots (on computer A), you can ensure that the second agent (on computer B) won't pick up on any scheduled or webhook-triggered TaskBots and you can use it for manual runs.
No, if the agent is inactive at the time when the scheduled run is supposed to start, then the scheduled run is skipped.
If a TaskBot is scheduled to run but it is already running, the new run will not be triggered. The currently active run will continue to run.
You can schedule for a different device, but you would need to restart your agent on the device where it's supposed to run on schedule (in this case device B).
As a desktop app, the agent cannot be called by the backend that operates on the cloud. (A desktop application can call the backend itself, but it cannot be called by it.) This is why it needs to be called from frontend (in other words, your scheduling or rescheduling action in the user interface triggers the agent to update the list of its scheduled jobs).
However, when you restart the agent, it will fetch all the updated scheduled jobs.
