Skip to content
Proud to collaborate with Microsoft for Startups

ticket.plan.propose ​

Attach an agent-authored fix plan to a ticket (supersedes any prior active plan).

Overview ​

PropertyValue
Workflow typeLinear
LibraryApp-tickets
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
organization_uuidstringYes——
ticket_uuidstringYes——
summarystringNo——
bodystringNo——
stepslistNo——
source_workflow_run_uuidstringNo——
proposed_by_typestringNo——
proposed_by_uuidstringNo——
extrajsonNo——

Output Schema ​

FieldTypeRequiredDefaultDescription
plan_uuidstringNo——
ticket_uuidstringNo——
statusstringNo——
supersededlistNo——
organization_uuidstringNo—Input field preserved in workflow state.
summarystringNo—Input field preserved in workflow state.
bodystringNo—Input field preserved in workflow state.
stepslistNo—Input field preserved in workflow state.
source_workflow_run_uuidstringNo—Input field preserved in workflow state.
proposed_by_typestringNo—Input field preserved in workflow state.
proposed_by_uuidstringNo—Input field preserved in workflow state.
extrajsonNo—Input field preserved in workflow state.
failed_atstringNo—ISO-8601 timestamp when action_fail recorded the failure
failure_reasonstringNo—Human-readable failure reason from action_fail
failure_typestringNo—Engine-stamped failure category
failed_actionstringNo—Engine-stamped action that raised
failed_at_statestringNo—Engine-stamped state when the workflow failed
failed_stepstringNo—Engine-stamped step name (DAG path)
failed_layerstringNo—Engine-stamped layer index (DAG path)
errorstringNo—Engine-stamped exception message
error_typestringNo—Engine-stamped exception class name

States ​

StateInitialTerminalSuccessAuto-advanceDescription
initiatedYesNo—executeAccepted
executingNoNo—completeApplying the mutation
completedNoYesYes—Done
failedNoYesNo—Failed

State Diagram ​

Transitions ​

FromActionToDescription
initiatedexecuteexecutingRun the mutation
executingcompletecompletedFinalize
* (any state)failfailedCatch-all failure

API Usage ​

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

{
  "workflow_type": "ticket.plan.propose",
  "initial_data": {
    "organization_uuid": "value",
    "ticket_uuid": "value"
  }
}