Skip to content
Proud to collaborate with Microsoft for Startups

schedule.update ​

Update a recurring schedule's name, cadence, target, inputs, or active state

Update a recurring schedule without deleting/recreating it.

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-composition
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
organization_uuiduuidYes——
schedule_uuiduuidYes——
target_workflow_typestringNo—Registered workflow type to start each occurrence
interval_minutesintegerNo—Minutes between runs (minimum 1)
namestringNo—Human-facing label
initial_datajsonNo—Inputs the run starts with (organization_uuid is injected automatically)
activebooleanNo—Whether the schedule should fire

Output Schema ​

FieldTypeRequiredDefaultDescription
scheduledictYes——
changed_fieldslistYes——
failure_reasonstringNo—Engine-stamped human-readable failure reason
failure_typestringNo—Engine-stamped failure category
failed_actionstringNo—Engine-stamped action method that raised
failed_at_statestringNo—Engine-stamped state when the workflow failed
failed_stepstringNo—Engine-stamped DAG step that failed
failed_layerstringNo—Engine-stamped DAG layer that failed
errorstringNo—Engine-stamped exception message
error_typestringNo—Engine-stamped exception class name

States ​

StateInitialTerminalSuccessAuto-advanceDescription
pendingYesNo—completeUpdate schedule
completedNoYesYes—Done
failedNoYesNo—Failed

State Diagram ​

Transitions ​

FromActionToDescription
pendingcompletecompleted—
pendingfailfailed—

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "schedule.update",
  "initial_data": {
    "organization_uuid": "value",
    "schedule_uuid": "value"
  }
}