Download all docs
io

Schedule

A clock that pulls the trigger for you: schedule fires a wired flow on a cron expression, timezone-aware and downtime-aware, so your automations run on their own without anyone standing by.

Working with it

Selecting a Schedule reveals its settings in the properties panel; it has no dedicated full-screen workbench.

How it appears

The same element type rendered as a definition, a circle instance, and a live workspace card.

Sc
type

Schedule

Fire flows on a time-based schedule using cron expressions

ioatomdefinition

When to use / not

When to use

  • Running a flow on a recurring wall-clock cadence — a nightly report, an hourly sync, a 'every 5 minutes' poll.
  • Driving work in a specific timezone, where the cron must be interpreted in local time rather than UTC.
  • Catching up (or deliberately skipping) runs that were missed while the platform was down, via the missed-run policy.

When not to use

  • A one-off delay before a single step — put a wait element inside an automation instead of standing up a recurring schedule.
  • Firing in response to an external event rather than the clock — an inbound HTTP call, queue message, or platform-trigger fits better.

Topology

Created from the library and placed inside an app or circle. It is a top-level building block you compose with other elements.

Properties

cronstring
Cron expression defining when to fire (e.g., '0 0 * * *' for daily at midnight)
timezonestring
Timezone for interpreting the cron schedule (IANA timezone name)

Capabilities

Inherited from io
  • Network
  • Observe

Operations

  • activityGET
  • attachmentsGET
  • batch_statsGET
  • composePOST
  • contextGET
  • createPOST
  • deleteDELETE
  • disablePOST
  • enablePOST
  • export_bundleGET
  • getGET
  • historyGET
  • import_bundlePOST
  • intentionGET
  • next_runsGET
  • promotePOST
  • readmeGET
  • readme_updatePOST
  • receivePOST
  • remove-modifierPOST
  • restorePOST
  • schemaGET
  • sendPOST
  • sourceGET
  • source_branchesGET
  • source_promotePOST
  • source_repairPOST
  • source_statusGET
  • source_validatePOST
  • statsGET
  • test_connectionPOST
  • treeGET
  • trigger_nowPOST
  • updatePATCH
  • update_metaPATCH
  • versionGET

Ports

Inputs

  • schedulerequest
  • eventevent

Composition

Errors / when it fails

Either cron or interval_seconds is required
Fails unless: (cron != null && len(cron) > 0) || (interval_seconds != null && interval_seconds > 0)

Validation rules

  • Interval under 60s may generate high load
  • Every-minute cron may generate high load (1440+ runs/day)

Schedule (schedule)

Category: io | Form: | Symbol: Sc

Fire flows on a time-based schedule using cron expressions

Fires a connected flow on a cron schedule. Set spec.cron to a cron expression (e.g., “0 */5 * * * *” for every 5 minutes) and spec.timezone for local time interpretation (defaults to UTC). The element emits a schedule event downstream at each tick. spec.overlap_policy controls what happens when the previous run is still executing. spec.missed_run_policy controls catch-up behaviour after downtime. Use trigger_now to fire immediately for testing without waiting for the next cron slot. Use next_runs to preview upcoming execution times. For one-off delayed execution, use the wait element in an automation instead.

Guide

Fire flows on a time-based schedule using cron expressions

What It Does

Schedule is an IO trigger that fires connected flows at regular intervals defined by a cron expression. It supports timezone-aware scheduling and configurable policies for handling missed runs after downtime.

Element Definition

PropertyValue
Typeschedule
Categoryio
Formatom

Key Properties

FieldTypeDefaultDescription
cronstringCron expression (e.g., 0 0 * * * for daily at midnight)
timezonestringUTCIANA timezone for interpreting the schedule
enabledbooleantrueWhether the schedule is active
missed_run_policystringskipHow to handle missed runs: skip, run_once, or run_all
max_concurrentinteger1Maximum concurrent executions

Usage

  1. Set a cron expression defining when to fire
  2. Wire the schedule to an automation or action element
  3. The connected flow executes automatically on each tick

Relationships

  • Uses: variable

Capabilities

  • cron: Standard cron expression scheduling (including seconds)
  • timezone: Timezone-aware schedule interpretation
  • overlap-control: Configurable overlap prevention (allow/skip/queue)
  • missed-run-recovery: Catch-up policy for runs missed during downtime

Properties

PropertyTypeDefaultDescription
cronstringCron expression defining when to fire (e.g., ‘0 0 * * *’ for daily at midnight)
timezonestring"UTC"Timezone for interpreting the cron schedule (IANA timezone name)
enabledbooleantrueWhether the schedule is active
missed_run_policystring"skip"How to handle missed runs after downtime. skip: discard missed slots. run_once: fire once to catch up regardless of how many were missed. run_all: fire once per missed slot.
overlap_policystring"skip"Behaviour when the previous run is still executing when the next tick arrives. allow: fire regardless (multiple concurrent runs allowed). skip: discard the tick if previous is still running. queue: enqueue the tick and run it as soon as the previous completes.
timeout_msinteger300000Maximum execution time per run in milliseconds before it is considered failed
target_operationstringOperation to dispatch on the target element when the schedule fires. Defaults based on target type: ‘invoke’ for actions, ‘call’ for http, ‘receive’ for messaging channels. Override when the default doesn’t match.
payloadobjectStatic payload included with every triggered event

Operations

activity

Get /ops/activity | Auth: Read

Get activity events for this element

Scope depends on element capabilities: individual elements query by element_id, project-form elements with activity-scope-members include member activities, circle-level elements with activity-scope-all query the entire circle. Gracefully returns empty list if activities table is missing (old circles).

attachments

Get /ops/attachments | Auth: Read

List all modifiers and resources attached to this element

Returns both modifiers (policy enforcement) and resources (data injection) with is_modifier flag to distinguish. Items in the generated MODIFIER_TYPES list are modifiers; everything else is a resource. Includes cascade_policy and version pin info.

batch_stats

Get /ops/batch_stats | Auth: Read

Get per-element statistics for all children of this element

Returns per-child stats plus an aggregate. Most meaningful on compound or manifest form elements (repositories, circles, projects); atoms have no children so the result is an empty children array with a zeroed aggregate. Uses efficient GROUP BY SQL. Weighted averages for eval scores.

compose

Post /ops/compose | Auth: Execute

Batch add and remove modifiers on this element in a single call

Declarative composition: add modifiers by ref path (slug or path@version) and remove by attachment ID, all in one atomic call on the target element. Each ‘add’ entry resolves the source element, validates topology, attaches with optional priority and cascade policy. Each ‘remove’ entry deletes the attachment row. Returns a summary of what was added and removed. Example: compose({ add: [{ref: “my-prompt”}, {ref: “rate-limit/api@v2”, priority: 50}], remove: [{attachment_id: “uuid”}] })

context

Get /ops/context | Auth: Read

Get connected elements (graph traversal)

Graph traversal showing all connected elements with their relationship type (contains, contained_by, references, referenced_by, attaches, etc.). Use ?depth=N to control traversal depth (default 1) and ?types=actor,data to filter by element types.

create

Post /ops/create | Auth: Write

Create child element

POST to the parent path — element_type goes in the request body, NOT the URL. Both element_type and slug are required and must be non-empty. Name is derived from slug if omitted. Writes to both Git and PostgreSQL. All elements are stored flat under the circle — no intermediate library wrapper rows.

delete

Delete /ops/delete | Auth: Admin

Delete element (soft delete)

Soft delete — sets state to ‘deleted’ but retains the record. Cannot delete elements that have children (has_no_bond precondition) or active runs. Requires admin auth and confirmation.

disable

Post /ops/disable | Auth: Admin

Disable element (hides and prevents use)

Idempotent — safe to call on already-disabled elements. Optionally pass a reason string. Disabled elements cannot be invoked or executed. Inverse of enable.

enable

Post /ops/enable | Auth: Admin

Enable element (makes usable and visible)

Idempotent — safe to call on already-enabled elements. Transitions element to ready/enabled state. Cannot enable deleted elements. Inverse of disable.

export_bundle

Get /ops/export/bundle | Auth: Read

Export element as downloadable git bundle

On non-root-namespace elements, returns a binary git bundle. On root-namespace (circle) elements, dispatch hands off to the circle’s own export_bundle op, which returns a multi-element JSON envelope with one base64 bundle per child element — this is intentional, not an error.

get

Get /ops/get | Auth: Read

Get element details

Element is already resolved by the routing layer — this returns the cached element, not a fresh DB query. Use the path /api/{circle}/{slug} to address elements.

history

Get /ops/runs | Auth: Read

List past scheduled runs

Lists past scheduled runs with their scheduled_at, executed_at, and status (completed, failed, skipped). Use to audit schedule execution reliability and identify missed or failed runs.

import_bundle

Post /ops/import/bundle | Auth: Write

Import git bundle into element

Accepts a base64-encoded git bundle in the JSON bundle_base64 field. Use overwrite=true to replace existing elements with same slug (default skips duplicates). Imported elements get new UUIDs. Returns counts of imported/skipped elements and any errors.

intention

Get /ops/intention | Auth: Read

Get element intention with full inheritance chain

Returns three levels: direct (this element’s intention), inherited (from category and root), and resolved (final merged intention). Useful for understanding an element’s purpose in context of its hierarchy.

next_runs

Get /ops/next-runs | Auth: Read

List upcoming scheduled execution times

Returns the next N scheduled execution timestamps based on the current cron expression and timezone. Use to verify the schedule is configured correctly before waiting for it to fire. Default count is 5.

promote

Post /ops/promote | Auth: Admin

Promote element configuration to a target environment

Only for manifest-form elements (projects). Environments advance: dev → demo → live. dev→demo requires member+ role, demo→live requires admin. Freezes member versions at promotion time (creates snapshot). Persists environment config to spec.environments.

readme

Get /ops/readme | Auth: Read

Get element README.md content

Reads README.md from the element’s git repository. Returns empty content (not an error) if no README exists. Always returns markdown format.

readme_update

Post /ops/readme_update | Auth: Write

Update element README.md content

Creates or overwrites README.md in the element’s git repo. Commits to the draft branch. Content must be provided as a markdown string.

receive

Post /ops/receive | Auth: None

Receive incoming external traffic

Entry point for external traffic reaching this IO element. Declared auth: none to bypass platform auth — element-level auth is enforced by IoReceiveExecutor before dispatching into the flow graph. The flow/app that wires this element as an entry point determines what happens next.

remove-modifier

Post /ops/remove-modifier | Auth: Execute

Remove an attached modifier from this element by attachment ID

Removes a modifier/resource attachment by its row ID. The ID comes from the attachments or context API. This is the reverse of attach — called on the target element, not the source.

restore

Post /ops/restore | Auth: Admin

Restore element to a specific version

Automatically snapshots the current state before restoring (creates a ‘Before restore to vN’ version entry). Writes restored spec to git as .triform/spec.yaml. Git failures warn but don’t fail the operation — DB state is authoritative. Cannot restore deleted elements.

schema

Get /ops/schema | Auth: Read

Get element input/output schema (MCP tools/list compatible)

Returns type-level port schemas from the TypeRegistry — not instance-specific overrides. Includes direction (input/output), required flag, and JSON schema per port. Useful for understanding what data an element accepts and produces.

send

Post /ops/send | Auth: Execute

Send a message/request to external system

Explicitly sends payload to the configured external target. For HTTP elements, POSTs to the target URL. For chat platforms, sends via the platform API. Put data in the payload field. Returns send status and response details.

source

Get /ops/source | Auth: Read

Get any file’s content from the element’s git repository

Reads an arbitrary file from the element’s CAS-backed git tree by its relative path. Same store as readme, just generalized. Path safety: rejects .. traversal, leading /, and null bytes. Use this to view main.py for action elements, asset files for SPAs, etc. Returns empty content (not an error) if the file doesn’t exist.

source_branches

Get /ops/source/branches | Auth: Read

List Source branches for this element

Returns the standard draft/demo/live Source branches, their current commits, and promotion relationships. Use GET /api/{element_path}/ops/source/branches.

source_promote

Post /ops/source/promote | Auth: Write

Promote Source branch forward

Promotes draft to demo or demo to live through the generated element op path. Direct Git pushes to demo/live are blocked by Source policy.

source_repair

Post /ops/source/repair | Auth: Write

Inspect or repair the element Source index

Runs Source repair through the element operation path. Defaults to dry_run=true; set dry_run=false only after reviewing a dry-run report.

source_status

Get /ops/source/status | Auth: Read

Get Source control status for this element

Returns the branch-aware clone URL, checkout commands, current draft commit, child source-link count, portable export summary, Source health, warnings, and auth hints for the addressed element. Use the element-first path: GET /api/{element_path}/ops/source/status.

source_validate

Post /ops/source/validate | Auth: Read

Validate Source branch contents

Validates a Source branch before accepting local Git workflow changes or promotion. Defaults to branch=draft and rejects runtime data, generated output, secret material, and unreadable CAS refs.

stats

Get /ops/stats | Auth: Read

Get aggregate statistics for this element

Health status is computed: error if errors_per_day > 5 or success_rate < 0.8, warning if errors_per_day > 0 or success_rate < 0.95. Firing alerts escalate health to error/warning. Default period is ‘day’. Returns runs_per_day, success_rate, avg_duration_ms, and more.

test_connection

Post /ops/test-connection | Auth: Execute

Test connection configuration

Validates the element’s configuration locally without making an actual external connection. Checks that required credentials are set, URLs are valid, etc. Returns success boolean and error details. Safe to call repeatedly.

tree

Get /ops/tree | Auth: Read

Get the element’s position in the graph — ancestors, children, references, and subtree statistics

Uses per-circle ElementGraph cache for O(1) lookups. Returns ancestors (containment chain), children (direct), members (references), referenced_by (reverse refs), attachments, and subtree stats. Default depth is 3, max is 10. Pass ?include_metadata=true for name/state on each node.

trigger_now

Post /ops/trigger | Auth: Execute

Manually fire the schedule immediately

Fires the schedule immediately, bypassing the cron timer. Returns run_id and triggered_at timestamp. Use for testing or when an on-demand execution is required without waiting for the next scheduled slot.

update

Patch /ops/update | Auth: Write

Update element

Partial update — send only the fields you want to change. spec, name, and intention are all independently optional. spec MUST be a JSON object when present; deep-merged into the existing spec by default. Empty {"spec":{}} preserves existing spec content but still records a new version (no-op for content, not for version state). To clear/replace the entire spec wholesale send {"spec":{...},"deep":false}. List-typed spec fields use replace semantics (the patch list replaces the existing list, no array merging). Coordinates Git + DB writes. Slug cannot be changed after creation.

update_meta

Patch /ops/update_meta | Auth: Write

Update element metadata (lightweight merge — does NOT bump version or snapshot spec)

Shallow JSONB merge into element.meta. Top-level keys in the provided value replace existing meta values; other keys are preserved. Used for UI metadata like canvas positions, panel state, viewer preferences. Wire-shape op_name is update_meta (distinct from update) so SSE subscribers + the cache auto-invalidator can distinguish lightweight metadata changes from spec edits without inspecting the payload. The MutatingElementStore wrapper stamps this op_name on the lifecycle event emitted by update_element_meta storage calls.

version

Get /ops/version | Auth: Read

Get current version or full history

Returns current version by default. Pass ?history=true for full version history (up to ?limit=N, default 50). Versions are backed by the element_versions table. Every spec update creates a new version entry.

Error Codes

CodeClassRetryableDescription
SCHEDULE_INVALID_CRONvalidationnoThe cron expression is not valid
SCHEDULE_INVALID_TIMEZONEvalidationnoThe specified timezone is not a recognised IANA name
SCHEDULE_OVERLAPconflictnoA run was skipped due to the overlap policy
SCHEDULE_TIMEOUTtimeoutnoA scheduled run exceeded spec.timeout_ms

Lifecycle / runtime

Inherited from io

Before request

  • validate_auth
  • check_rate_limit

After request

  • record_metrics

On error

  • log_error
  • retry_if_transient

Execution model: async

Observability

Defined for this element

Metrics

  • execution_count
  • missed_run_count
  • skipped_run_count
  • execution_duration_ms
  • drift_ms
  • manual_trigger_count

Events

  • schedule.fired
  • schedule.completed
  • schedule.failed
  • schedule.missed
  • schedule.skipped
  • schedule.manual_trigger

Pricing / cost

Platform default

Operation costs

  • create: free
  • update: free
  • delete: free
  • get: free
  • list: free
  • invoke: 10000 micro-AU
  • tool_use: free

Set it up

Schedulestring
When to trigger (cron expression)
Timezonestring