Inputs and outputs
A workflow input’s name and a project field’s id are separate values. Bind an input to a visible field of the required type and schema. Declare output destinations explicitly; those fields carry their workflow source.
A missing required card input refuses a fire. An optional input is omitted only when its declaration permits it. Changing an input binding is different from disconnecting and recreating a connection.
Rules
A rule names its trigger, conditions and actions. Read the current trigger and action schemas before constructing one. A connection, a rule and a run are separate records; inspect each when an automation does not begin.
What completion proves
The automation wall records dispatch and outcomes. A finished build is evidence of that run. Pull request creation, review, landing and installation require their own receipts. Do not infer them from a task’s displayed status.
Recover deliberately
A locked output needs its source fixed. An approval tied to an older base needs a current review. Access and refusals explains how to keep the server’s named cause intact.