Checking Workflow Status

Workflows, jobs, and other stages (such as pulling containers and setting up volumes) can have the following values for status:

Pending: the workflow/job/subtask is waiting for available resources to run or is dependant upon another job/subtask to start
Started: the workflow/job/subtask has started and is running on available compute resources
Finished: the workflow/job/subtask ended without errors
Errored: the workflow/job/subtask ended with errors

select

Please select either the GUI or CLI tab to see the appropriate instructions for your environment.

GUI

It’s easy to check the status of workflows in the GUI. Just select the workflow that you want to check in the “Workflows” tab and a dashboard will open giving you detailed information about the workflow and the individual workflow jobs and stages.

Fuzzball dashboard showing a running workflow status

There is a larger section at the top (“WORKFLOW OVERVIEW”) showing information about the entire workflow, and two smaller sections (“PULL IMAGE” and “RUN JOB”) showing the subtask that pulled the image and the job itself. Clicking on the job section (for the job called “printer”) shows info about the job status on the right. In this example, the job has started but has not yet finished. You can also see the assigned Universally Unique Identifier (UUID) of the container in which the job is running.

CLI

To check the status of a workflow using the Fuzzball CLI, you can issue the following command:

$ fuzzball workflow describe <workflow UUID>
Name:      printer.fz
Email:     dgodlove@ciq.co
UserId:    74a78835-1601-4364-a85c-0eee707b8017
Status:    STAGE_STATUS_STARTED
Created:   2024-05-14 03:42:35PM
Started:   2024-05-14 03:42:35PM
Finished:  N/A
Error:


Stages:
KIND     | STATUS   | NAME                                 | STARTED               | FINISHED
Workflow | Started  | b0955d8c-bb5f-4ac2-994b-84d1634bcfbd | 2024-05-14 03:42:35PM | N/A
Image    | Finished | docker://alpine:latest               | 2024-05-14 03:42:36PM | 2024-05-14 03:42:50PM
Job      | Started  | printer                              | 2024-05-14 03:43:04PM | N/A

In this case, you can see that the workflow itself is named “printer.fz” in reference to the Fuzzfile that was used during submission. The workflow has the status “Started” indicating that there are jobs or stages that have not yet completed. The “Image” subtask (which refers to the operation of pulling the image from the registry) has the status “Finished” indicating that it completed without errors. And the (lone) job named “printer” has the status “Started” indicating that it is still running.