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

### Graph Events

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

#### Types of graph events

- Graph started

- Graph phase finished

- Graph finished

- Graph error

- Graph aborted

- Graph timeout

- Graph unknown status

#### Graph started

Graph started event is created, when ETL graph execution successfully started.

#### Graph phase finished

Graph phase finished event is created, everytime when graph phase is finished and all its nodes are finished with status `FINISHED_OK`.

#### Graph finished

Graph finished event is created, when all phases and nodes of graph are finished with `FINISHED_OK` status.

#### Graph error

Graph error event is created, when graph cannot be executed for any reason, or when any node of graph fails.

#### Graph aborted

Graph aborted event is created, when graph is explicitly aborted.

#### Graph timeout

Graph timeout event is created, when graph runs longer than for a specified interval. Thus you should specify a "Job timeout interval" attribute for each listener of a graph timeout event. You can specify this interval in seconds or in minutes or in hours.

Figure 24.2. Web GUI - graph timeout event

#### Graph unknown status

Graph 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 the graph run. Server automatically changes state of a graph to Not Available and sends a graph unknown status event.

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

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