Starting and Stopping Your New Workflow
Now that you have a Fuzzfile loaded into the web UI or saved on your file system for use with the CLI, you are ready to have fun running you first workflow!
Submitting your workflow to Fuzzball with the web UI is easy. If you followed the steps to use the printer example from the Workflow Catalog in the previous section, you simply need to press “Continue” in the lower right hand corner of the dialog box.
If you opened the printer example in the workflow editor, (or if you have another Fuzzfile loaded in the workflow editor) simply press the triangular “Start Workflow” button in the lower right corner.
Either way, you will be prompted to provide an optional descriptive name for your workflow.
Now you can click on “Start Workflow” in the lower right corner of the dialog box and your workflow will be submitted. If you click “Go to Status” you can view the workflow status page.
If you leave the workflow running, you can use it to complete the following sections on Interacting with workflows. But if the workflow times out, or you click the red button labeled “Cancel” you can always click the green “Rerun” button on the same page to start a new workflow from the same Fuzzfile.
Assuming you created and cd-ed into a new directory and created the file printer.fz in the
previous section on building workflows, the command that you need to
submit the workflow follows.
$ fuzzball workflow start printer.fz
Workflow "3cc718d1-e35c-4455-b4f4-ca3412727277" started.
As shown above, Fuzzball assigns each workflow a Universally Unique Identifier (UUID) upon submission. This UUID serves as the primary reference point when you need to control, monitor, or interact with your workflow. For instance, to stop the workflow we just started, we would execute:
$ fuzzball workflow stop 3cc718d1-e35c-4455-b4f4-ca3412727277
Workflow stopped with name 3cc718d1-e35c-4455-b4f4-ca3412727277
The remainder of the quick start guide will use the syntax <workflow uuid> whenever you need to
substitute your specific workflow’s identifier in a command.
Please be aware of this known issue causing your Fuzzfiles to be changed by the Fuzzball Orchestrate engine upon workflow submission.