Taskflows

Back Next

Advanced properties

You can configure a taskflow to disable concurrent execution. You can also configure a taskflow to suspend on a fault at the taskflow level and send an email notification to specified recipients when it is suspended.

You can define the following advanced properties for a taskflow:

Property	Description
Concurrent taskflow execution	Enables or disables concurrent taskflow execution based on the option that you select from the following list: Allow concurrent execution (Default) . When you select this option, the taskflow execution is enabled so that multiple instances of the taskflow can run at the same time. By default, concurrent execution is enabled. Disable concurrent execution . When you select this option, the taskflow execution is disabled. When you select this option, the taskflow does not create a new instance when another instance is still running. Enable concurrent execution with unique instance names . When you select this option, multiple instances of the taskflow that have unique instance names can run at the same time. For more information, see Any error that occurs during the concurrent taskflow execution will be displayed only when you run the taskflow as an API or by using the RunAJob utility. Before you can run the taskflow again, you must wait for a minimum of 5 seconds or until the confirmation message stating that the taskflow has started disappears. This option is not applicable if you use the taskflow in a Subtaskflow step.
Suspend on Fault	Suspends the taskflow on a fault that occurs at the taskflow level. The Suspend on Fault property takes precedence over the following properties that you define in a Data Task step: Fail taskflow on completion - if this task fails Fail taskflow on completion - if this task does not run If you enable the Suspend on Fault property in the parent taskflow, the taskflow continues to show as running if a subtaskflow fails.
Send Email on Suspension	Sends an email notification when the taskflow is suspended on a fault. When you select the Send Email on Suspension option, the Email To , Email Cc , Email Subject , and Email Body fields become available. You can parameterize these fields by using the parameter set, input fields, output fields, and temporary fields. For example, when you move assets from one Point of Deployment (POD) to another, instead of manually entering the recipient Cc email addresses, you can parameterize them to save time.
Email To	Defines the primary recipients for the email notification. Enter one or more valid recipient email addresses. You can also add fields that contain valid email addresses. Separate email addresses and fields with a comma (,) or a semicolon (;). Required if you configure the taskflow to send an email notification on suspension.
Email Cc	Defines the recipients who need to be sent a copy of the email notification. Enter one or more valid recipient email addresses. Separate email addresses with a comma (,) or a semicolon (;).
Email Subject	Specifies a short and descriptive subject that introduces the email.
Email Body	Defines the content that you want to send in the email. Click Edit Content to open a rich text editor and use formatting options such as bold, italics, underlines, lists, indentations, and fonts. You can also insert tables and links.

Concurrent taskflow execution scenarios

Consider the following scenarios when you configure the

Allow concurrent execution (Default)

option for a taskflow:

Before you switch from the

Allow concurrent execution (Default)

option to the

Disable concurrent execution

option or vice versa, you must unpublish the taskflow and ensure that the previous taskflow instance is executed. You can then switch to another option in the

Concurrent taskflow execution

list and publish the taskflow.

When a previous taskflow instance is in a suspended state, even if you run the taskflow again,

Data Integration

does not run the taskflow instance.

When a taskflow instance is running, you can run a previous taskflow instance from a step that ran successfully using the

Run from here

option on the

My Jobs

page in

Data Integration

, and the

All Jobs

and

Running Jobs

page in Monitor.

The parent taskflow and subtaskflow run independently. For example, you have a taskflow that contains a subtaskflow with the

Allow concurrent execution (Default)

option enabled for both the taskflows. When you run the parent taskflow, the child taskflow runs as a subtask. When you run a taskflow or subtaskflow independently, it runs for the first time without any issue. However, if you run the same taskflow or subtaskflow again while the previous instance is still running, an error occurs.

When you run a taskflow using an endpoint, if the previous instance of the taskflow is still running, an error occurs. However, if you run the same taskflow several times from the taskflow designer, you see a success message. This is because when you run a taskflow,

Data Integration

receives a request and sends an immediate response as

200 OK

Data Integration

processes the taskflow run request later. This is for a better user experience because taskflows might take time to run depending on their complexity.