Polling nodes are used to trigger the execution of tasks continuously at a given time interval, after completing previous execution.

> All the nodes can be used within the Start and End Polling nodes. Polling node can be executed only from the execution mode (not design mode).

The execution of polling nodes is continued until it is stopped manually, irrespective of child tasks whether they are successfully executed or failed. So, this can be considered as a scheduler which can trigger the execution of other child tasks at a given time interval.

While exporting a polling task, it will export related child tasks as well.

Conditions

• Only task nodes are allowed within the polling nodes. In case if any other nodes are used, the polling will not be executed and the status in the Polling History and Execution Summary screen will be updated as INVALIDATED.
• No iterations are allowed within the polling nodes.
• RESTART functionality will not be available for polling tasks.

Propeties Of Start Polling Node

• Name: Name of the node. A default name is displayed in this field, which the user can edit according to the task and the intent of using the node.
• Description: A short note on the purpose of the node.
• Delay (in seconds): Minimum delay is 15 sec by default.

Propeties Of End Polling Node

• Name: Name of the node. A default name is displayed in this field, which the user can edit according to the task and the intent of using the node.
• Description: A short note on the purpose of the node.

Refer to Database Automation with Polling sample task to know how to use Polling nodes in a task.