Stalled Recurrences

Categories:
Tags:
New to psLens? This page documents one specific alert. To see how it appears on the dashboard, what operators investigate, and how teams tune it, start with a live walkthrough.
Book a Demo Browse Alerts
Tailored Operational Context
  • Target Database: —
  • Context Type: —
  • Alert Severity: —
  • Triggered Time: —
  • Firing Context: —

Stalled Recurrences Alert

Alert ID: stalled_recurrences Category: Process Scheduler Default lookback: 336 hours (14 days)

What This Alert Detects

This alert fires when a scheduled recurring process has finished a run recently (within the lookback window) but does not have a subsequent scheduled instance.

In PeopleSoft, the Process Scheduler is responsible for scheduling the next run of a process based on its recurrence definition when the current one runs. If the scheduler is interrupted, a database is refreshed, or an error occurs during the scheduling process, the recurring job can fall off the schedule. This check identifies those occurrences so they do not go unnoticed.

Severity Logic

ConditionSeverity
The latest completed run failed (status was Error, Not Successful, or Unable to Post) and no next run is scheduledCritical
The latest completed run succeeded or was cancelled and no next run is scheduledWarning

What Gets Checked

The alert queries PSPRCSRQST for all process requests that have a recurrence name assigned. It then groups these requests by:

  • Process Name (PRCSNAME)
  • Run Control ID (RUNCNTLID)
  • User ID (OPRID)
  • Recurrence Name (RECURNAME)

For each unique combination, if the latest instance has a completed status and there are no active/pending requests (such as Queued, Blocked, Hold, Pending, Initiated, or Processing) to follow, the recurrence is flagged as stalled.

Alert Details

When firing, the alert produces an item for each stalled recurrence:

  • Summary: Recurrence RECURNAME for PRCSNAME — Stalled (Last status: STATUS)
  • Details:
    • prcsName: The process name
    • runCntlId: The run control ID
    • oprid: The user ID that submitted the process
    • recurName: The recurrence definition name
    • lastInstance: The process instance number of the last run
    • lastRunStatus: The status of the last run (e.g. Success, Error)
    • lastRunDttm: The date and time the last run was scheduled

Configuration

alerts:
  checks:
    stalled_recurrences:
      enabled: true
      lookbackHours: 336   # How far back to look for completed runs (14 days)
SettingDefaultDescription
lookbackHours336How many hours back to look for the last completed run of a recurrence.

How to Respond

  1. Click the link in the alert detail to view the last process instance in the Process Monitor.
  2. Check the logs for that instance if the status was an error.
  3. If the recurrence should continue running, go to PeopleSoft and submit the process again on the same recurrence name using the matching User ID and Run Control ID.
  4. If the recurrence has intentionally finished its life cycle (e.g., reached its end date), you can ignore the warning or configure the process in the exclusions list.