Workflow diagrams

What you get

• A diagram for every workflow
• Each step coloured by its recent runs
• Decisions and approvals drawn as their own shapes
• Timing, retries, input and output for each step
• A warning when the code and the diagram differ
• Replay from a run's page

How it works

Each workflow in whisk.yaml names a small graph file: its steps, the decisions between them and where each one leads. The step names are the names the code uses, so the diagram describes the workflow that really runs.

The dashboard draws the graph and colours each step by its recent runs: green ran, red failed, blue running, grey never ran. Open a run to see every step with its timing, retries, input and output.

whisk doctor warns when the code and the graph list different steps. The dashboard marks the difference too. Run data comes from Inngest, the open-source engine behind durable workflows.

Example

A freight forwarder's operations manager opens the customs entry workflow and sees that the filing step failed three times this week. Each run's page shows what the broker's system answered, without anyone reading logs.

For your coding agent

# workflows/customs-entry.graph.yaml
steps:
  - id: fetch-shipment
  - id: needs-permit?
    branches: { yes: request-permit, no: file-entry }
  - id: request-permit
    kind: approval
    next: file-entry
  - id: file-entry

whisk functions graph customs-entry prints the declared steps beside the ones runs took. The graph field is in the whisk.yaml reference, and the graph format is in the agent instructions.