Process Run Check

Process Run Check Alert

Alert ID: process_run_check Category: Process Scheduler

What This Alert Detects

This alert monitors configured critical processes and fires when one has not completed successfully within its expected time window. It is the alert equivalent of the Process Run Check report. The difference is that this runs automatically on every check cycle and surfaces failures on the dashboard without any manual action.

Use this alert for processes that must run on a regular cadence, such as:

• Nightly batch jobs that must complete before business hours
• Data synchronization processes that run every few hours
• Critical integrations that should run multiple times per day
• Post-maintenance verification of essential processes

Severity Logic

Configuration

Process checks are configured per process name in config.yaml. Each entry specifies the process name and the number of hours within which a successful run is expected.

alerts:
  checks:
    process_run_check:
      enabled: true
      processChecks:
        SOMEJOBNAME: 24      # Must run successfully within 24 hours
        ANOTHERJOB: 8        # Must run successfully within 8 hours
        NIGHTLY_ETL: 12      # Must run successfully within 12 hours

If a process name is listed with 0 or a negative value, the check defaults to a 24-hour window.

What Gets Checked

For each configured process, psLens queries PSPRCSRQST for successful runs (RunStatus = 9 / Success) within the configured time window. If none are found, it then checks for any run history to determine severity:

• No successful run in window + recent run history found: Warning
• No run history at all: Critical

Alert Details

Each alert item includes:

• Process name
• Configured threshold (hours)
• Last known run status (if any history exists)
• Last known run time (if any history exists)
• Link to the Process Definition detail page

How to Respond

1. Click the alert link to open the Process Definition detail page for the affected process
2. Review recent run history to understand what happened. Did the process run but fail, or did it not run at all?
3. Check the Process Scheduler server configuration if the process never ran
4. Investigate error logs if the process ran but ended in a failed state
5. If the process ran and succeeded but outside the expected window, consider adjusting the threshold in config.yaml

Tables Queried