Metadata Manager 10.4.0
- Metadata Manager 10.4.0
- All Products
If you run multiple instances of a workflow concurrently in a series, a small number of the workflows might enter an aborted state. The issue is observed when 180 instances of a single workflow run in a cycle 100 times with the default Data Integration Service memory heap memory allocation.
When you assign the system parameter sys:ApplicationName or sys:MappingName to a Mapping task input in a workflow, the Mapping task input parameter does not read the system parameter values. Instead, the Mapping task input parameter reads the default value of the mapping parameter at run time.
If the Data Integration Service restarts while a workflow is running, the Monitoring tool might fail to report that the workflow entered a cancelled state.
The issue can arise when the domain uses different Model Repository Services to store the workflow metadata and to monitor the workflow.
If a workflow contains parallel Mapping tasks and you cancel the workflow while the Mapping tasks are running, any mapping that has yet to start proceeds to run.
The issue arises when the following conditions are true:
Workaround: Increase the Maximum Worker Threads value.