If you upgrade to the current version and you update a workflow in the Model repository, you cannot deploy the workflow application.

When a Mapping task does not generate exception data for a downstream Human task in a workflow, the workflow fails.

Early selection optimization can cause filter logic to occur before expression logic in a mapping. When this situation occurs, you might receive unexpected results.

You cannot validate a workflow that contains multiple Mapping tasks if you replace the data target in a mapping that one of the tasks uses.

The search and replace options in an exception task do not recognize Float data types as numeric data when the task is in a Microsoft SQL Server database.

You cannot use the All Numbers option to replace a numeric value on all pages of exception task data in a Microsoft SQL Server database.

You cannot search and replace data in a column in an exception task if the workflow that created the task used the column data to distribute task instances to users.

If you create the workflow database contents on a Data Integration Service on grid and the Data Integration Service stops unexpectedly, the Administrator tool displays the following message:

Workflow log file names do not include a time stamp.

You cannot deploy a workflow application if the workflow contains more than 12 Mapping tasks between two Inclusive gateways.

When you run a workflow with a Mapping task under an operating system profile, the workflow does not create the directories that the operating system profile specifies. In addition, the Mapping task fails to run.

You cannot use the Scheduler to run mappings, workflows or any other job in a domain where Kerberos authentication is enabled.

If you select the ODBC provider as MongoDB and Cassandra to connect to the source, the Data Integration Service cannot push transformation logic to the source and results in a null pointer exception.