Scheduling
Use a schedule when a bot must run on its own at recurring times, for example every weekday at 9 AM (0 9 * * 1-5). A schedule defines when (Cron expression), which bot and version, and where (agents) it runs, with no manual intervention. It’s ideal for monitoring routines, data extraction or periodic automations.

Data Table
| Field | Description |
|---|---|
| Bot | Name of the bot associated with the schedule. |
| Version | Specific version of the bot scheduled for execution. |
| Mode | Execution mode (headless, parallel, interface). |
| Agent | Agents configured for the schedule. |
| Cron Expression | Configured cron expression. |
| Next Execution | Indicates the date/time of the next job execution. |
| Status | Indicates whether the schedule is active or inactive. |
| Actions | Item actions Edit, Delete. |
Filters
| Filter | Description |
|---|---|
| Bot | Filters schedules by bot |
| Agent | Filters by agent |
| Status | Filters by ON/OFF status |
New Schedule
Below is the description of the fields needed to configure a schedule.

Cron Expression
- Description: Defines the frequency and execution time of the bot. The expression follows the standard Cron format, allowing flexible scheduling.
- Example:
* * * * *(Executes every minute) - Tip: Use the visual Cron expression generator available on the platform to facilitate creating the desired expression.
| Field | Description | Notes |
|---|---|---|
| Bot | Bot that will be executed when the trigger is fired. | Must be previously created and available on the platform for selection. |
| Version | Specific version of the bot to be used. | Accepts X.Y.Z (example: 1.0.0) or release, which always uses the latest available version. |
| Label | Optional identifier for the trigger. | Can be used for organization or filtering. |
| Agent | Defines the agent responsible for bot execution. | The agent must be active and connected. Multiple agents can be selected, avoiding execution bottlenecks. |
| Parameters (JSON) | Additional parameters sent to the bot, in JSON format. | Reach the code as environment variables. Example: {"arg1": "1366", "arg2": "768"} |
| Description | Free text describing the trigger’s purpose. | Makes it easier to identify on listing screens. |
Execution and Error Limits
Optional features to control the volume of queued executions and how the schedule behaves when failures happen. All of them are disabled by default and are turned on individually through a Enabled/Disabled option; once enabled, the corresponding quantity is requested.
Limit Queued Executions
- Default value:
Disabled - Description: Restricts the maximum number of executions the schedule can keep queued at the same time. While the limit is reached, no new executions are created until one of them finishes.
- Available options:
Enabled,Disabled. - Important: When enabled, you must provide the maximum number of queued executions.
Automatically Retry on Error
- Default value:
Disabled - Description: Makes the schedule automatically try to run the bot again whenever an execution finishes with an error.
- Available options:
Enabled,Disabled. - Important: When enabled, you must provide the number of automatic retries allowed.
Disable Schedule After a Number of Errors
- Default value:
Disabled - Description: Automatically deactivates the schedule (Status changes to OFF) once it reaches the configured number of errors.
- Available options:
Enabled,Disabled. - Important: When enabled, you must provide the number of errors tolerated before automatic deactivation.
Tip
The three features can be combined. For example: allow up to 3 automatic retries per failed execution and automatically disable the schedule after 5 errors.
Cron Generator
The platform offers a visual generator to facilitate creating Cron expressions. Below are the tabs available for configuration: Allows defining execution frequency based on minutes.

Available Settings
Minutes
- Description: Defines the minutes when the bot will be executed.
- Available options: Every X minute(s), Specific minute, Minute interval.
Hours
- Description: Defines the hours when the bot will be executed.
- Available options: Every X hour(s), Specific hour, Hour interval
Day
- Description: Defines the days of the month when the bot will be executed.
- Available options: Every X day(s) starting on Sunday, Every x day(s) starting on the first day of the month, Specific day of the month, Day interval
Month
- Description: Defines the months when the bot will be executed.
- Available options: Every X month(s), Specific month, Month interval
Cron Expression Examples
0 9 * * 1-5: Executes the bot at 9 AM Monday through Friday.30 14 * * 6,0: Executes the bot at 2:30 PM on Saturdays and Sundays.0 */2 * * *: Executes the bot every 2 hours.0 0 1 * *: Executes the bot at midnight on the first day of each month.
Edit Schedule
To edit an existing schedule, click the icon in the Edit column.
Note
The editing fields are the same as the creation form. For more details about each field, see the New Schedule section.

Remove Schedule
To remove a schedule, click the trash icon in the Actions column.
Tip
A confirmation modal will be requested.
Disable Schedule
To deactivate or activate a schedule, click the toggle in the Status column.
Tip
A confirmation modal will be requested.