Workload Prioritizer Insights enhances the existing System page, transforming it from a snapshot of raw counts into a helpful tool for diagnosing issues and prioritizing next steps. This Early Access feature supports Operators and integration analysts who monitor, troubleshoot, and triage workload issues in CIC, by allowing them to see what’s happening in the system, understand why, and act on it, all from one place.
- Monitor system capacity: See how much headroom your system has at a glance.
- Track queue depth trends: Watch how queue depth changes over time instead of relying on a single snapshot.
- Get plain-language diagnoses: Automated analysis explains what’s going on in clear, readable terms.
- Fix issues with one click: Apply recommended remediations directly from the diagnosis.
Viewing and Managing System-level Information
A new panel joins System Status, Active Processes, and Queued Processes. The Utilization panel displays Active Process utilization against your tenant ceiling in real time. This helps to identify sustained periods running near system maximums to distinguish whether backlog is due to priority misconfiguration or global capacity constraints.
Combined with all panels, this provides a system-level insights perspective that lets you know when basically CIC is slowed down because it's hitting your system max. At one glance you can determine if you have an effective processes in order to sustain the business needs.
Queue Health Findings
Queue Health Findings automatically analyzes queue performance to identify the underlying causes of slowdowns. Using deterministic, rule-based detection, it examines queue behavior and highlights the specific issues contributing to reduced performance. This gives you clear insight into what is actually going wrong, rather than simply indicating that a problem exists.
Findings flag specific operational conditions, including priority contention, where lower-priority or background work competes with and starves high-priority queues. They also flag concurrency contention, where queues compete with each other for available worker slots before reaching tenant limits, and global concurrency ceiling issues, where worker capacity is saturated across multiple queues at once.
Each finding describes the root cause in plain language and includes a confidence score, so you can quickly judge how strongly the evidence supports it and decide where to act first.
Working with your findings
After clicking Analyze with AI, WLP Insights reviews the last few minutes of queue activity and lists any problems it finds as findings. Each finding has a severity (Critical or Warning) and a confidence level (High or Medium), and it comes with a recommended action.
Expand a finding to determine issue and possible course of action. The Apply Action button appears only when every recommended change is a Max Active or Priority change on a named queue. Otherwise no button appears. Affected queue names are links that open that queue's detail.
The Active Processes tab lists every process running on your system at the moment, so it’s where you act on findings that WLP Insights can’t fix with an Apply Action button, such as stuck jobs. You can search the list to find the processes a finding refers to, then cancel them one at a time or several at once. Cancelling always asks for confirmation first.
The table below shows the same examples shown above. Each is a different kind of problem: a queue limited by its own settings, jobs that have stopped making progress, and a tenant running out of workers.
The last column indicates whether the finding includes an Apply Action button. This appears only for Max Active or Priority changes on a named queue. Otherwise, apply the recommendation yourself.
Always review every suggested action before applying it, because findings are optimized for total throughput only.
| Finding | Severity / Confidence | What's wrong | Recommended action | Apply Action? |
|---|---|---|---|---|
| Queue held back by its own limit (ReceiveEdiEvent) | Critical / Medium | 128 items queued, 2 of 2 workers busy, about 19 of 60 tenant workers idle | Raise Max Active from 2 to 5 | Yes |
| Stuck jobs (AcmeRemittancePickupEV) | Warning / High | 3 runs active for up to 56m with no progress, holding 3 of 4 workers | Cancel the runs in Active Processes, then check the SFTP connection | No |
| System Max reached daily (Outbound846InventoryEV) | Warning / Medium | All 60 workers busy for 436 min on 6 of the last 7 days | Stagger the schedule or cap Max Active. Request a higher System Max if volume keeps growing | No |
Queue Trends
Historical trend charts let you track queue depth for every queue over periods from the past hour to 30 days, making it easier to spot recurring patterns and compare volumes over time. Surge detection continuously monitors trends to catch sudden spikes and gradual backlog buildup early, so teams can respond before performance or service levels are affected.Business process visibility lets you see which active processes are running within each queue through queue-to-process mapping. Drill-down navigation then lets you inspect any individual process to trace its parent queue lineage.
New Visual Status Indicator
A new Health column in the Events tab displays for each queue, showing an immediate health status (Healthy, Warning / Elevated, or Critical). This allows you to quickly monitor and identify queue health levels.
Comments
0 comments
Please sign in to leave a comment.