JAMS Scheduler V7.9.2 Release Notes
Note:
Review the Advisories and Manual Intervention Notices to see if you need to complete additional manual steps for an installation or upgrade.
Enhancements
Web Client
Sequence Tab for Monitor Entries - You can now track Sequence Jobs in real time directly from the Web Client. The new Sequence tab on the Monitor Entry detail page shows the live task tree with color-coded status, plus the ability to skip, hold, release, or retry tasks.
System API Tokens - JAMS now lets administrators issue API tokens so scripts, integrations, and monitoring tools can call the JAMS REST API without a user signing in interactively. Tokens are created and managed from a new API Tokens page under Access in the Web Client.
Scheduler
Improved Scalability for File Watches - File Watches now scale far more efficiently on the backend. Previously, each File Watch consumed a dedicated scheduler thread. At high volumes, this could lead to thread exhaustion. File Watch monitoring is now aggregated to minimize the number of threads needed.
Fixes
Scheduler
Resolved an issue where notification email addresses supplied by Variables could resolve to an empty value, causing the Scheduler to retry sending indefinitely and eventually exhaust memory.
Resolved an issue where Jobs using the PowerShellCore execution method fail with an unhandled exception.
Resolved an issue where Jobs carrying Resource Requirements inherited from several levels of the Folder tree could saturate the database connection with redundant updates, slowing Job completion and growing the message queue.
Resolved an issue where JAMSServer could fail to stop, or run at elevated CPU, in a High Availability environment.


