The parent task the graph ran as, when it was dispatched. Absent for a folded graph.
What to call it, as typed in the card.
Asked here rather than in a dialog (ratified answer ④): one field and a button keeps the capture at two seconds. A saved workflow gets NO trigger from this path — it runs on demand until someone gives it a schedule — because the moment of saving is about capture, not scheduling.
True when the user asked to continue in the editor rather than just save.
A secondary route on purpose: making the editor mandatory turns a two-second capture into a task, which is the friction that stops good one-off plans becoming reusable.
ReadonlyNameWhat to call it, as typed in the card.
Asked here rather than in a dialog (ratified answer ④): one field and a button keeps the capture at two seconds. A saved workflow gets NO trigger from this path — it runs on demand until someone gives it a schedule — because the moment of saving is about capture, not scheduling.
ReadonlyOpenTrue when the user asked to continue in the editor rather than just save.
A secondary route on purpose: making the editor mandatory turns a two-second capture into a task, which is the friction that stops good one-off plans becoming reusable.
ReadonlyParentThe parent task the graph ran as, when it was dispatched. Absent for a folded graph.
ReadonlySpec
Fired when the user asks to promote this plan into a reusable workflow.