Evose

Schedule

Unified scheduled triggers for Agent / Chatflow / Workflow · 6 modes · State machine

Schedule is the Workbench's unified scheduling entry point. Configure a schedule on any Agent / Chatflow / Workflow and it will run automatically.

Supported App Types

AppRequiredOptional
Prompt Agentmessage (instructions to the Agent)
Chatflowmessageinputs (start node parameters)
Workflowinputs (start node parameters)

6 Scheduling Modes

ModeConfigurationExample
onceA single timestampRun once on 2026-06-01 09:00
intervalInterval (min/hr/day)Run every 30 minutes
dailyEvery day at HHEvery day at 09:00
weeklyDay of week + timeEvery Monday at 09:00
monthlyDay of month + timeThe 1st of every month at 09:00
cronCron expression0 9 * * MON-FRI (workdays 09:00)

Live preview of next runs

Once configured, the schedule card immediately shows the next 5 execution times for visual verification.

State Machine

[Active] ←─┐
   │       │
   ↓ pause │ resume
[Paused] ──┘

   ↓ done (once)
[Completed]

   ↓ reactivate
[Active]
StateBehavior
ActiveParticipates in scheduling + allows manual trigger
PausedDoes not schedule + allows manual trigger
CompletedTerminal state for once mode; can be reactivated

Run Records

Every execution (whether scheduled or manual) produces a run record:

FieldDescription
Sourceschedule / manual
Statusrunning / success / failed
LatencyTotal execution milliseconds
Start/end timeUTC + user time zone
Input / outputFull snapshot
TraceJump to Trace for node-level detail

Records belong to the schedule

Even if the schedule is deleted, run records are retained (for audit).

Notifications

When execution completes, the creator receives an in-app message:

  • Success / failure status
  • One-line summary
  • Click into the run record details

Concurrency

The same schedule allows concurrent execution (independent records, no blocking).

Example: runs every 5 minutes, but a single run takes 8 minutes — the schedule still creates a new run every 5 minutes, so 1–2 parallel executions may exist. If your business doesn't allow concurrency, lock inside the app.

Variables

The message field supports template variables:

VariableMeaning
{{start_time}}The scheduled start time of this run (user time zone, YYYY-MM-DD HH:mm:ss)

Example:

Generate the sales report for the 24 hours before {{start_time}}.

MVP Limitations

The current MVP does not yet support (on the roadmap):

  • Event triggers / Webhook triggers (partially supported in Workflow triggers — see Workflow)
  • Retry policy configuration
  • Cross-task DAG dependencies
  • Canary / multi-environment
  • After deletion, records cannot be recovered

Full roadmap

Next Steps

On this page