Table of Contents

Search

  1. Preface
  2. Taskflows and linear taskflows
  3. Taskflows
  4. Linear taskflows

Taskflows

Taskflows

Advanced properties

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
Skip if Running
Disables concurrent taskflow execution.
When you select this option, the taskflow does not create a new instance when another instance is still running.
If you run the taskflow before the previous instance is complete, the request fails.
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
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.
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.

Skip if running scenarios

Consider the following scenarios when you enable the
Skip if Running
option for a 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
    Skip if Running
    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
    or as an API
    , 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.
  • When you run a taskflow with the
    Run Using
    option and click
    Run All
    to run the taskflow using multiple inputs, you might see an inconsistent behavior.
    For example, you have three taskflow inputs and you run the taskflow with all three inputs. All three requests are triggered at once. Therefore, you might see that sometimes the taskflow runs with one input and sometimes with two inputs.
    This is because when you run a taskflow with multiple taskflow inputs, multiple requests are triggered at once.
    Data Integration
    checks if there is any existing instance running. Each request is considered as the first request and attempts to run a taskflow.

0 COMMENTS

We’d like to hear from you!