# No Process Completed
LLMS index: [llms.txt](/llms.txt)
---
-
Target Database:
—
-
Context Type:
—
-
Alert Severity:
—
-
Triggered Time:
—
-
Firing Context:
—
## No Process Completed Alert
**Alert ID:** `no_process_completed`
**Category:** Process Scheduler
**Default lookback:** 1 hour
## What This Alert Detects
This alert fires when **no process has successfully completed** within the configured lookback window. It is a broad scheduler health check. If nothing has finished successfully in the past hour, the Process Scheduler may be down, stalled, or not dispatching jobs.
This is distinct from the [Process Run Check](/docs/alerts/process-scheduler/process-run-check/), which monitors specific named processes. This alert monitors overall scheduler activity.
## Severity Logic
| Condition | Severity |
| -------------------------------------------------- | -------- |
| Zero successful completions in the lookback window | Warning |
## What Gets Checked
The alert queries PSPRCSRQST for any process with **RunStatus = 9 (Success)** and an end datetime within the lookback window. If no rows are returned, the alert fires.
Only one result is needed to resolve the alert. The check uses a limit of 1 for efficiency.
## Alert Details
When firing, the alert produces a single item:
- Summary: `No process completed successfully in the last N hour(s)`
- Lookback hours used for the check
## Configuration
```yaml
alerts:
checks:
no_process_completed:
enabled: true
lookbackHours: 1 # How far back to look for completed processes
```
| Setting | Default | Description |
| --------------- | ------- | ----------------------------------------------------------------- |
| `lookbackHours` | `1` | How many hours back to look for a successfully completed process. |
## How to Respond
1. Check PeopleSoft's Process Monitor to see if any processes are running, queued, or have recently completed
2. Verify the Process Scheduler server is running (PeopleSoft > PeopleTools > Process Scheduler > Servers)
3. If processes are queued but not running, the scheduler daemon may need to be restarted
4. If this fires regularly during off-hours when no jobs run, increase `lookbackHours` or disable the alert for those periods
## Tuning
If your environment has periods where no batch jobs are expected to run (e.g., overnight maintenance windows), consider increasing `lookbackHours` to cover those gaps, or disable the alert entirely during those windows.