Executions
Overview of workflow executions
After the login you are in the tab "Executions". An execution describes the concrete processing of a "Submission Information Package" (SIP) by means of a specific workflow.
All SIPs are listed,
- that are being processed
- whose processing is completed
- whose processing was terminated due to an error.
The list consists of several columns that contain information on processing:
| Example | Description |
|---|---|
291 | ID: unique processing number |
Quality Assurance, Migration and Storage | Name of the workflow, that processes the SIP. |
sip: additional_sip.zip | List of inputs and their values |
| Status | The status column shows a dot for each processing step of the relevant workflow. Its color indicates the status: brown: this step is still pending. yellow: this step is currently being executed. green: this step was completed successfully. red: this step failed. black: this step was skipped. |
| Created at | Time at which the execution was created. |
| Started at | Time at which the process was started. |
| Duration | Time elapsed since the start. |
The delete link can be used to delete this information from the database. This deletion has no influence on the result of the corresponding workflow, only the information about the corresponding execution is deleted.
By using the Filter button, you can filter the list of executions by workflow, status, SIP/Deposition, creation date and execution start date.
Details of an execution
The link show takes you to a detail view of a specific execution.
The detail view provides information on the status of the individual steps that together form a workflow. If a step has been successfully completed, it is marked in green and the next step is started. If a step fails, this is displayed in red.
Failed steps can be restarted (feeder then tries to execute the failed step again) or ignored (feeder then continues with the next step). When ignoring steps, please note that this can lead to problems with subsequent steps if these are dependent on the skipped step.
A running workflow execution can be stopped. A stop signal is sent and the step is displayed as stopped after the signal has been executed. Stopped steps can be restarted or ignored in the same way as failed steps. If the step is already complete when the stop signal is processed, it is displayed in green and the workflow stops before the next step is executed.
Depending on the log level set, more or less information is displayed for the individual workflow steps. By clicking on the downward arrow (displayed on the right of each step), this information can be displayed or hidden.
In addition to the log informations, system administrators see the feeder runner who did execute the step.
