# Backlogged Processes
LLMS index: [llms.txt](/llms.txt)
---
-
Target Database:
—
-
Context Type:
—
-
Alert Severity:
—
-
Triggered Time:
—
-
Firing Context:
—
## Backlogged Processes Alert
**Alert ID:** `backlogged_processes`
**Category:** Process Scheduler
**Default threshold:** 30 minutes
### What This Alert Detects
This alert finds Process Scheduler requests that are in **Queued** or **Blocked** status and whose scheduled run time (`RUNDTTM`) has already passed by more than the configured threshold.
### Severity Logic
| Condition | Severity |
| ------------------------------------------- | -------- |
| Overdue by more than `thresholdMinutes` | Warning |
| Overdue by more than `thresholdMinutes × 2` | Critical |
For example, with the default threshold of 30 minutes:
- A process scheduled 40 minutes ago that is still queued → **Warning**
- A process scheduled 65 minutes ago that is still queued → **Critical**
### What Gets Checked
The alert queries the Process Scheduler request table for processes in run status **5 (Queued)** or **18 (Blocked)** whose `RUNDTTM` (scheduled run datetime) is in the past. For each result, it calculates how far past the scheduled time the process is based on `RUNDTTM` and the current server time.
Processes with no `RUNDTTM` value are skipped.
### Alert Details
Each alert item includes:
- Process name (`PRCSNAME`)
- Process instance number
- How long the process is overdue (in minutes)
- Current run status (Queued or Blocked)
- The operator who submitted the request
- A link to the Process Monitor detail page for that instance
### Configuration
```yaml
alerts:
checks:
backlogged_processes:
enabled: true
thresholdMinutes: 30 # Minutes overdue before flagging as Warning
excludeProcesses: # Process names to skip
- SOME_LOW_PRIORITY_JOB
```
| Setting | Default | Description |
| ------------------ | ------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| `thresholdMinutes` | `30` | Minutes past the scheduled run time before a queued/blocked process triggers a Warning alert. Critical fires at 2× this value. |
| `excludeProcesses` | `[]` | List of process names to exclude from this check. Use for processes that are known to queue for a long time and are not a concern. |
### How to Respond
1. Click the alert link to go directly to the Process Monitor entry for the flagged process
2. Check whether the Process Scheduler server is running and accepting work
3. Look at how many processes are currently running on the server. It may have hit its concurrency limit
4. Check if the process type or class has reached its maximum allowed concurrent instances
5. For blocked processes, investigate what is blocking them (dependencies, server restrictions, etc.)
6. If the Process Scheduler server is down, restart it from PeopleSoft's Process Scheduler administration
### Tuning the Threshold
The right threshold depends on how busy your Process Scheduler is. In environments where many jobs are submitted at once, some queuing is normal. Set `thresholdMinutes` high enough to avoid false positives during peak batch windows but low enough to catch genuine problems. You can also use `excludeProcesses` to exclude specific low-priority processes that are known to queue for long periods.