PS Query & SQL

 View Only

  • 1.  Catching Process Scheduler issues before users complain

    Posted 5 hours ago

    I’m curious how others are approaching Process Scheduler visibility today.

    Across several higher-education PeopleSoft environments I’ve worked with, one recurring challenge is that batch issues aren’t always obvious failures — they’re often late executions, silent contention, or restart patterns that don’t surface until business impact occurs, especially during off-hours.

    Even when institutions use enterprise schedulers or monitoring tools, I’ve noticed that a lot of the visibility gaps still live inside PeopleSoft itself — around request lifecycle behavior, queue contention, and restart handling.

    For those supporting PeopleSoft Finance / HCM / CS today:

    • Are you relying mainly on external schedulers or monitoring tools?
    • Custom scripts or queries?
    • Manual checks and email alerts?

    I’d be interested to hear what’s working well (or not) in real-world operations.



    -------------------------------------------


    ------------------------------
    Tirumala Rao Chimpiri
    Senior Programmer Analyst
    Stony Brook University
    ------------------------------

    Message from the :
    ------------------------------
    Find, Review, and Engage with Higher Education-focused solution providers, products, and services using the .
    ------------------------------
    Alliance 2026 Registration is Open!


  • 2.  RE: Catching Process Scheduler issues before users complain

    Posted 43 minutes ago

    I only support the Financial Aid module for CS, so I can only tell you what I'm personally doing.  But, your question might have been more of a "as an institution... "

     

    All scheduled jobs send me an email with failure/success.  If I know something shouldn't have failed when it did, I'll investigate.  If I don't get a success when I expected it, I'll investigate.  I have once a day jobs, once a week jobs, every hour or every other hour jobs.  It's easy to know what I can delete and what I have to investigate though.

     

    For FA, the packaging and repackaging processes will run to success but get a failure.  We have a script that runs at specific times every day looking for specific words like "DATA CORRUPTION".  If it finds it, it sends me the process instance number so I can investigate.

     

    On top of this I have specific jobs I'm tracking run times for so I can easily identify when something is running longer than usual.  We have some big jobs though 500 to over 1200 processes, so if one section is all of a sudden running longer, we need to look into that.

     

    That's just for FA (at my school).

     

    Dana Pawlowicz

    Business Systems Analyst Sr - ERP

    Business Enterprise Systems and Technologies
    Digital Technology Solutions

    University of Cincinnati

    51 Goodman Dr.

    Cincinnati, Oh 45221

     

     




    Original Message
    Alliance 2026 Registration is Open!


Related Content