If you parameterize an expression in a mapping in advanced mode and specify a function in the

mapping

task that isn't available in advanced mode, the

mapping

task incorrectly validates the expression. If you run the

mapping

task, the job fails.

Mapping tasks fail at run time when all the following conditions apply:

The task is based on a mapping in SQL ELT mode.
The source and target connections and objects are parameterized.
In the mapping task, the source type is set to "Query," and you enter a custom query.

Validation fails for a mapping task in which all the following conditions apply:

The task is based on a mapping in SQL ELT mode.
The source and lookup connections and objects are parameterized.
Any field names in the lookup condition are identical to each other or to a source field name.

When you run a mapping task that is based on a mapping in SQL ELT mode, the job details page displays the target name in the individual source and target results as "Target (Target1)" instead of including the actual target name inside the parentheses. If there are multiple targets in the mapping, the success rows and error rows displayed for "Target (Target1)" are cumulative for all targets.

When you create a mapping task using the new mapping task editor, you can't create an advanced relationship for the parameterized source objects.

When a taskflow that contains multiple parallel tasks is configured to send an email on suspension, an email is sent for each failed or suspended task. This results in multiple email notifications to the recipients.

If you save changes that you made to an asset that's checked out and then undo the checkout, the changes aren't reverted. If you undo the checkout using an undoCheckout API request, you'll receive an error message. However, if you undo the checkout in the user interface, you won't receive an error message and the action will appear to be successful in the source control log.

When you monitor a

dynamic mapping

task and drill down on an individual job, the page stops responding.

When the scheduler fails to trigger the scheduled taskflow job for the first time, the scheduler service doesn't perform a retry.