Home | Table of Contents | Jobflow Events | CloverETL 4.6.1
--- | --- | ---
Prev | Jobflow Event Listeners | Next

### Jobflow Events

Each event carries properties of the event source job. If there is an event listener specified, task may use these properties. E.g. next job in the chain may use "EVENT_FILE_NAME" placeholder which activated the first job in the chain. Job properties, which are set specifically for each run (e.g. RUN_ID), are overridden by the last job.

##### Types of jobflow events

- Jobflow started

- Jobflow phase finished

- Jobflow finished

- Jobflow error

- Jobflow aborted

- Jobflow timeout

- Jobflow unknown status

#### Jobflow started

A Jobflow started event is created, when jobflow execution successfully started.

#### Jobflow phase finished

A Jobflow phase finished event is created, everytime when jobflow phase is finished and all its nodes are finished with status `FINISHED_OK`.

#### Jobflow finished

A Jobflow finished event is created, when all phases and nodes of jobflow are finished with status `FINISHED_OK`.

#### Jobflow error

A Jobflow error event is created, when jobflow cannot be executed from any reason, or when any node of the jobflow fails.

#### Jobflow aborted

A Jobflow aborted event is created, when jobflow is explicitly aborted.

#### Jobflow timeout

A Jobflow timeout event is created, when jobflow runs longer then specified interval. Thus you have to specify "Job timeout interval" attribute for each listener of jobflow timeout event. You can specify this interval in seconds or in minutes or in hours.

Figure 24.7. Web GUI - jobflow timeout event

#### Jobflow unknown status

A Jobflow unknown status event is created, when the server, during the startup, detects run records with undefined status in the executions history. Undefined status means, that server has been killed during jobflow run. Server automatically changes state of jobflow to Not Available and sends jobflow status unknown event.

Please note, that this works just for executions, which have persistent record in executions history. It is possible to execute transformation without persistent record in executions history, typically for better performance of fast running transformations (e.g. using Launch Services).

Prev | Up | Next
Jobflow Event Listeners | Home | Table of Contents | Listener