Fluxos de trabalho

Automação que corre sobre eventos: cada fluxo é um gatilho e os seus passos, o rascunho edita-se no lugar, e só a versão publicada recebe tráfego. O separador de execuções mostra cada uma com o seu estado e a sua razão: uma falha traz o seu erro, uma espera nomeia o seu sinal.

The library

Each card is one workflow: its name, its enabled switch, how many runs are inside it right now and when it last changed. The switch stops a workflow taking new runs without touching its definition. Last-run and runs-today numbers come from an aggregate over all runs, not from the visible page, and a workflow whose numbers have not loaded shows a dash rather than a zero, because zero is a claim that nothing ran.

The steps editor

Opening a card unfolds a two-tab fold: Steps and Runs. The steps editor writes the workflow as sentences: the trigger (fired by hand or by a cohort signal), then each step in order, actions with their kind and settings, delays, branches with their cases and an otherwise, jumps that loop back with a guard against looping forever. Edits land in a draft that saves as you work; Publish is the separate, deliberate act that puts a version in front of traffic, and its dialog shows what the published version will replace and names its refusal when the engine rejects a graph rather than failing silently. Problems the draft already has are listed on the card before publish is even offered.

The runs tab

Every run with its state: queued, running, waiting, completed, failed or cancelled. A waiting run names the signal it waits for and offers sending it; a failed run carries the error that stopped it, whichever shape the engine reported it in; opening a run steps through what each node did. Fire once starts a run by hand, and a run that should stop can be cancelled. Failed and waiting runs also surface on the Home screen's Needs you list, with the same actions.

Copiar para… na linha abre a cópia de configuração já com este objeto marcado; consulte Projetos, Copiar a configuração.

Where this meets the API

The concept behind the screen is the Workflows pillar. On the wire: the library is workflowDefinitions with workflowDefinitionStats for the numbers; authoring is createWorkflowDefinition, updateWorkflowDefinition and publishWorkflowVersion; operation is setWorkflowEnabled, fireWorkflow, signalWorkflow and cancelWorkflow; runs read through workflowRuns and workflowRunSteps and update live on the workflowRunChanges subscription (GraphQL reference). Triggers gate on cohorts.