Module 08 | TRACK B: chain steps into a repeatable recipe

Use a uniquely named JSON file

The existing Email King workflow is user state and remains untouched. The course files live under reference and are the recovery copies.

Use Windows paths in PowerShell.

Track A may skip this module.

Missions remain the file-free multi-agent route.

Run in your terminal

armaraos workflow list
armaraos workflow get <EXISTING_ID>

Field	Role
`prompt_template`	Text sent to the step; `{{input}}` is workflow input.
`output_var`	Name for a result that a later step can reference.
`mode`	Sequential in the verified file.
`error_mode`	Fail in the verified file.
`timeout_secs`	Per-step time ceiling.
`collect_aggregation`	Null in the verified file.

Keep the source file because workflow has no export.

Run in your terminal

armaraos workflow create <COURSE_FILE>

Both two-step and minimal stored-shape files were rejected. Do not rewrite existing state to investigate.

Run in your terminal

armaraos workflow run <WORKFLOW_ID> "<INPUT>"
armaraos workflow update <WORKFLOW_ID> <FILE>
armaraos workflow delete <WORKFLOW_ID>

These become valid only after your own create returns an ID. This build did not.

Keep both rejected files, the error output, the version number, and the unchanged workflow list.

Check it / preserve existing state

List workflows, confirm Email King is unchanged, and point to the rejected course files.

Safety note

Never experiment on an existing workflow you did not create for the lesson. Update and delete require an exact ID, and deletion has no undo.

Troubleshooting for this sitting

What you see	Likely cause	What to do
Invalid workflow step	Verified 0.8.3 create defect.	Preserve file and error; stop.
An existing workflow appears	It belongs to current state.	Do not repurpose or delete it.
JSON flag errors	Workflow has no JSON options.	Use its normal output.
Run needs an ID	Course create never succeeded.	Do not use another workflow's ID.