Scheduled trigger

A scheduled trigger launches an execution automatically, at the time or frequency you define with a cron expression. This is what turns an automation into something that truly runs alone: ​​every night, every Monday, every 15 minutes, without anyone having to remember.

Create a scheduled trigger

1. Enter the environment and open the Triggers tab.
2. Click New trigger.
3. Enter a name (e.g. Conciliación nocturna).
4. Select the Scheduled type.
5. Select the process, the agent and the robot session with which each execution will run.
6. Enter the cron expression and timezone.
7. Guarda.

From there, Zoan Cloud creates a run every time the clock matches the cron expression, in the chosen time zone.

The cron expression

The cron expression defines the schedule. For example, 0 8 * * 1-5 means “Monday to Friday at 8:00 a.m.” You have the complete reference with examples in Cron Expressions.

Zona horaria

The time is interpreted in the time zone you select, not UTC by default. Choosing the right one is essential for the process to run when you expect.

Colombia

Use America/Bogota (UTC-5, no daylight saving time).

Beware of daylight saving time (DST)

If your area applies daylight saving time, a run scheduled at a specific time may skip or repeat on the day of the change. For critical processes, avoid scheduling them in the time slot where the adjustment occurs (usually early morning).

Activar y desactivar

You can enable or disable a trigger at any time from the list, without deleting it. A disabled trigger does not generate executions even if its scheduled time arrives — useful for pausing a process during maintenance or while you correct something, without losing its configuration.

What should be programmed?

Schedule processes that must occur on their own, recurrently, and at a known time — without anyone having to remember to launch them.

Buen candidato a programar	Example
Tareas recurrentes de calendario	Bank reconciliation every night; sales report every Monday 8 a.m.
Processes that depend on a closure or cut	Billing at month-end; payroll biweekly
Periodic surveys	Check a mailbox or folder every 15 minutes
Feed a queue (dispatcher)	Queue the day’s invoices at 6 a.m. for bots to process
Mantenimientos fuera de horario	Cleaning or backups at dawn, when the systems are free

Do not schedule it if the process is triggered by a specific action (launched by a person when needed → manual execution or manual trigger) or if it depends on an unpredictable external event instead of the clock.

Programar vs. cola

They are not exclusive, they are combined: the scheduled trigger decides when the work starts; the queue distributes that work among several bots. The typical pattern is a trigger that, at a fixed time, launches the dispatcher process that fills the queue.

Good practices

• Verify first with a manual execution that the process runs well, and only then schedule it.
• Ensures there is an agent online in the scheduled slot. If the process runs at 2 a.m., the agent (ideally an unattended service) must be on and logged in at that time.
• Do not overlap executions: if a process can take longer than the interval between runs (e.g. every 5 min but sometimes it takes 8), take this into account so as not to accumulate executions.
• An explicit time zone avoids surprises; Don’t depend on default values.

Next steps

• Expresiones cron — sintaxis y ejemplos.
• Agent Monitoring — ensure availability at the scheduled time.
• Run Logs — check that automatic runs are working.