Visual workflows
Schedule workflows with an explicit timezone
A scheduled workflow uses a cron expression and a timezone to determine when it runs. Kition provides frequency choices, an advanced cron field, and a preview of the next runs.
Updated
By Kition Docs
Verified against Kition 0.2.0 (7d49036f) on 2026-11-06
Make the intended timezone explicit
A time such as 09:00 is incomplete without a timezone. Specify the business timezone and inspect the schedule preview before enabling the workflow. This is especially important when the person configuring the schedule and the machine running Kition are in different places.
The Frequency choices are Every day, Every weekday (Mon–Fri), Every Monday, Every hour (top of hour), and Custom (advanced). The Cron expression uses five fields: minute, hour, day of month, month, and day of week. New schedules start in your computer’s timezone; an empty timezone means the server’s local time.
Configure a schedule
- Choose At scheduled time as the trigger in the workflow editor.
- Choose a Frequency and Time of day, or choose Custom (advanced) and edit the Cron expression directly.
- Set the Timezone to an IANA name such as America/New_York rather than leaving it empty.
- Read Next run and the following runs in the preview, and fix any cron or timezone error it reports.
- Save the workflow, test its actions, and enable it only after the input and timing are correct.
Review the schedule as a whole
| Setting | Question |
|---|---|
| Frequency | How often should this business process run? |
| Time of day | Will the required inputs be ready by then? |
| Timezone | Whose local time does this mean? |
| Preview | Do the next runs match your intent? |
| Availability | Will Kition be running at those times? |
Distinguish scheduling from guaranteed execution
A valid expression does not prove that a task will succeed. Connections, data, and the running app still matter. Inspect Run History after the first scheduled run instead of assuming that the schedule preview confirms delivery.
For workflows with external effects, consider what happens if one run takes longer than expected or fails. Do not assume catch-up, deduplication, or overlap behavior without testing it. Keep the timing simple until you understand the process under normal operation.
Version and sources
This guide describes the Kition desktop app as of source 7d49036f, checked on 2026-11-06. Connected actions also depend on the configured model provider or service. If your installed version is older, some controls may differ.
Related pages
Choose a workflow trigger and source table
A workflow trigger defines when a process starts and which record reaches its actions. Choosing the right trigger and required fields prevents work from running on the wrong records.
Inspect workflow runs and diagnose failures
Workflow run history is the record of executions and their outcomes. It connects a configured process with evidence of what actually happened.
Test a workflow with representative sample data
A workflow test runs a configured action against a real row. It helps uncover missing fields and connection problems before the workflow is enabled.