Skip to main content

Execution States in the UnifiedViews Execution Monitor

Abstract

Execution States in the UnifiedViews Execution Monitor

This section contains a short guide on the individual execution states visible in the Execution Monitor.

SCHEDULED

SCHEDULED state means that the pipeline execution record is stored in the database, but the execution has not started. The pipeline execution in this state is created by scheduler, execution is scheduled for the exact date and time. Also the pipeline execution in SCHEDULED state can be created in case of pressing Run or Debug pipeline buttons when the backend is offline.

RUNNING

RUNNING means that the pipeline currently is in execution state. For each running pipeline the staging data for each DPU in the pipeline are stored in the staging database . The data are stored under automatically generated names. Also a record about execution is stored in database. The record contains last finished DPU.

CANCELLING

CANCELLING state is an interim status. It appears after you have clicked Cancel when the pipeline has been in RUNNING or SCHEDULED states. The execution record will remain in the CANCELLING state until the execution is CANCELLED.

26411284.png
CANCELLED

CANCELLED state means that the pipeline execution has been interrupted by the Cancel button.

FAILED

FAILED state means that the pipeline execution started, but a fatal unrecoverable error has occurred somewhere in the execution process.

Therefore the pipeline execution has not finished, which means that a loader has not loaded all the data (or any at all) being processed into intended destination. Graphs in the staging database cannot be deleted in this state, so they may be used for debugging.

FINISHED SUCCESS

FINISHED SUCCESS state means that the pipeline execution finished without any reported errors, a loader successfully loaded all the data into the knowledge base.

FINISHED WARNING

FINISHED WARNING state means that the pipeline execution finished, however some recoverable errors occurred during execution. Graphs in the staging database cannot be deleted in this state, so they may be used for debugging.