Stalled Recurrences

Categories:
Tags:
New to psLens? This page documents one specific report. To see how it runs in the product, what the output looks like, and how teams use it in practice, start with a live walkthrough.
Book a Demo Browse Reports
Tailored Operational Context
  • Target Database: —
  • Context Type: —
  • Alert Severity: —
  • Triggered Time: —
  • Firing Context: —

Stalled Recurrences Report

Report ID: stalled-recurrences Category: Process Scheduler

Purpose

This report identifies scheduled recurring processes that have completed a run recently but do not have a subsequent scheduled instance.

In PeopleSoft, recurring batch schedules are kept active by the Process Scheduler, which automatically schedules the next run when the current run starts or completes. However, issues like database refreshes, scheduler outages, cancellations, or errors can cause a schedule to stall without generating a future instance. This report lists all such stalled recurring processes to ensure they can be resumed.

The report answers: “Which of my recurring batch processes have stopped scheduling?”

Parameters

ParameterDefaultDescription
lookback_days14The window in days. The report checks for recurring processes that completed their last run within this window but have no future runs.

Tables Queried

PSPRCSRQST — Process Request Instances

The report queries PSPRCSRQST to fetch historical and future instances that have a recurrence name assigned:

SELECT PRCSINSTANCE, PRCSNAME, RUNCNTLID, OPRID, RECURNAME, RUNSTATUS, BEGINDTTM, ENDDTTM, RUNDTTM
FROM PSPRCSRQST
WHERE RECURNAME <> ' '
  AND COALESCE(BEGINDTTM, RUNDTTM) >= TO_DATE('{cutoff}', 'YYYY-MM-DD')

Data Flow

1. Calculate the lookback cutoff date based on 'lookback_days'
        |
        v
2. Query PSPRCSRQST for all requests with a recurrence name since the cutoff date
        |
        v
3. Group requests by (PRCSNAME, RUNCNTLID, OPRID, RECURNAME)
        |
        v
4. For each group:
   - Identify active/pending instances (Queued, Blocked, Hold, Pending, Initiated, Processing, Posting, Restart)
   - Identify completed instances (Success, Error, Cancelled, etc.)
   - If there is at least one completed run, but ZERO active/pending runs:
     - Mark the recurrence as stalled
     - Find the latest completed instance
        |
        v
5. Generate the Markdown report:
   - Summary count of stalled recurrences
   - Table of stalled recurrences with last run status and links
   - Troubleshooting recommendations

Report Output

The generated report contains:

  • Header displaying the database name, run ID, and lookback window.
  • Summary showing the count of stalled recurrences detected.
  • Results Table with columns: Process Name, Recurrence, User, Run Control, Last Instance, Last Status, and Last Run Date/Time.
  • Recommendations detailing the resolution steps.

Interpreting Results

If a recurrence is listed in the report, it has stopped running. Check the Last Status column:

  • Error / Not Successful / Unable to Post: The schedule stopped due to a process failure. The scheduler may not have been able to queue the next run, or the recurrence was stopped.
  • Success / Success with Warning / Cancelled: The process ran or was cancelled but did not reschedule. This could happen if the recurrence ended naturally (reached its end date), or if it was manually cancelled and not rescheduled.