Run the execution plan manually - 7.3

Talend Administration Center User Guide

Version
7.3
Language
English
Product
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Module
Talend Administration Center
Content
Administration and Monitoring
Last publication date
2024-02-20

About this task

This procedure explains how to run an execution plan manually. For more information on how to schedule it with triggers, see Scheduling an execution plan.

Procedure

  1. On the Execution Plan page, select the execution plan.
  2. Click Run on the toolbar to execute the tasks according to the order and conditions set in the hierarchical view.
    Note: You can add triggers to any plan to schedule its execution based on time or event, using time triggers or file triggers respectively. For further information, see Scheduling an execution plan.

    Example

    Upon completion of the execution, the preceding icons at respective nodes light up if their tasks have been launched. Meanwhile, the status of the executed tasks will appear in the square brackets on the right.
    The table below explains these icons:

    Icon

    Description

    The OnOk node's task has been launched. The status of execution is given in the square brackets on the right.

    The OnError node's task has been launched. The status of execution is given in the square brackets on the right.

    The After node's task has been launched. The status of execution is given in the square brackets on the right.

    Once the plan has been executed, you can also visualize its execution details (logs, history, advanced information) by clicking the corresponding icons in the Actions column of the Execution Plan page. To display the execution details of a specific task, select it in the central panel, right-click and select Display last execution details. For more information, see Monitoring task executions in the Monitoring node.