When multiple task flows run against the same databases, it can be hard to track execution status, identify scheduling conflicts, or prevent one workload from overwhelming shared resources. Task Orchestration Operation Center gives you a central place to edit task flows, monitor running instances, analyze scheduling distribution, and cap the number of SQL statements a database handles concurrently.
Prerequisites
Before you begin, ensure that you have:
-
Access to the DMS console
-
At least one task flow created in Data Management (DMS)
Go to Task Orchestration Operation Center
-
Log on to the DMS console V5.0.
-
In the top navigation bar, choose O&M > Task Orchestration Operation Center.
In simple mode, hover over theicon in the upper-left corner and choose All functions > O&M > Task Orchestration Operation Center.
Manage task flows
Click Task Flow Management. Find the task flow you want to manage and use the actions in the Operation column:
| Action | What it shows |
|---|---|
| Edit | The directed acyclic graph (DAG) of the task flow |
| Published Tasks | All published versions |
| Running History | Runtime history |
From this page, you can also view execution duration trend charts for both scheduled and manually triggered runs, and publish or unpublish multiple task flows at once.
Monitor task flow instances
Click Instance Management. The Instance Management page shows a live view of all task flow runs.
What you can do here:
-
View instance statistics — The Instance Statistics section shows the total number of runs, broken down by successful and failed.
Statistics are based on the time instances ran, not the business date. To switch to a business-date view, select Business Date to the right of the Owner field.
-
Filter by state — Narrow the list to instances in the Running, Success, or Fail state.
-
Check a task flow's status — See the current state of any task flow at a glance.
-
Review execution duration — Click Execution History in the Operation column to see duration trend charts for both scheduled and manually triggered runs.
View scheduling distribution
In the Scheduling Statistics section, select an execution time range and the task flows you want to inspect. DMS renders the scheduling time distribution as a Gantt chart, making it easy to spot overlaps or gaps in your scheduling plan.
Limit concurrent SQL statements on a database
When multiple task flows target the same database, they compete for the same connection pool. Use the monitoring and assurance feature to set an upper bound on how many task flows can run SQL statements on a given database at the same time. This protects database stability and prevents any single workload from monopolizing shared resources.
How the concurrency limit works:
| Behavior | Details |
|---|---|
| Concurrency cap | Resource Quota sets the maximum number of task flows that can run concurrently on a database |
| Queue when over limit | If running task flows exceed the quota, DMS queues the excess task flows in a priority queue |
| Priority range | 1–10; higher values run first |
| Queue timeout | If a task waits longer than the maximum wait time configured on its task node, it stops queuing and is marked as failed |
To set a concurrency limit:
-
Go to the Task Orchestration Operation Center page.
-
Click Monitoring and Assurance. On the Concurrency Configuration tab, click New.
-
In the Add Concurrency Configuration dialog, set Resource Type, Resources, and Resource Quota, then click OK.
For example, setting Resource Quota to 20 means at most 20 task flows can run on the specified database at the same time. Any additional task flows wait in the priority queue until a slot opens.