Workflow runs

Once you have imported or created workflow version(s), you are ready to create associated Workflow Runs, to document the execution of these workflows with actual data.

While you can directly import workflow runs from a Galaxy instance (so-called "invocations" in Galaxy), for other workflow managers there are currently 2 options to register Workflow Runs:

1. manually create a workflow run in the web interface
2. use the command line interface (CLI) to register workflow runs (see register workflow runs with the CLI)

We have illustrated both options (manual vs CLI) for 2 different use-cases : imaging and sequencing in follow up tutorials (see outline on the left).
The use-cases cover similar aspects so you can pick the use-case that is most familiar to you and just follow this one.

About workflow runs

By Workflow Runs, we mean here the execution of a particular Workflow Version on input datasets using specific configuration & parameters, typically resulting in the creation of output datasets.
Registering workflow runs in LabID allows to easily keep track of all this information:
- version of the workflow used for the run
- datasets used as input
- output datasets generated by the run
- additional metadata about the run (command line options, execution status, date of execution...)