JAMS Scheduler V7.9.5 Release Notes
Note:
Review the Advisories and Required Manual Intervention notice before you upgrade. The 7.9.5 release replaces MSMQ with NATS.io, which is not compatible with the Legacy Web Client or Legacy API. Some environments need manual steps.
Important Changes in Behavior
Read this section before you upgrade.
Scheduler
NATS Replaces MSMQ - JAMS services now communicate through NATS instead of Microsoft Message Queuing (MSMQ). You no longer need to install MSMQ. The installer creates the NATS certificates for you. See Advisories and Required Manual Intervention for port, firewall, and failover guidance.
Always Resubmit On by Default - New Interval Triggers now have Always Resubmit selected by default. Existing triggers keep their current setting.
Certificate Organization Name - Certificates that JAMSRegister creates now list JAMS Software as the organization. Existing certificates are unchanged.
Web Client
Legacy Web Client and Legacy API are not compatible - The Legacy Web Client and Legacy API are not compatible with JAMS 7.9.5 due to the move to NATS. If you rely on either one, stay on JAMS 7.9.2 until you move to the current Web Client and REST API. The Legacy Web Client reaches end of life on March 31, 2027.
Web Client Security
LDAPS Certificate Validation - User Federations that connect with ldaps:// now validate the domain controller’s certificate. The certificate must chain to a certificate authority that the Web Client host trusts. If your domain controllers use self-signed certificates, update your trust configuration before you upgrade.
Disabled and Expired Accounts - Directory accounts that are disabled or expired, and users of a disabled User Federation, can no longer sign in. This includes System API Tokens tied to those accounts.
Ownership for SSO Users - A user who signs in through an Identity Provider (ADFS, Entra ID, Okta, or a custom OIDC or SAML 2.0 provider) now gets full access to the Folders, Jobs, Variables, Resources, and Credentials they create. This matches how LDAP User Federation users already work.
Installer
Integration Packs Included - Integration Packs now install with their main component (Agent, Agent Interactive, Client, or Scheduler). The separate Integrations page has been removed.
Encryption Key Prompt for New Databases - When you create a new JAMS database, the installer now asks you to set a new encryption key or restore an existing one. It no longer uses the default key without asking.
Batch Job Logon Rights - The installer no longer changes the “Log on as a batch job” security policy.
New Features
Web Client
SLA Risk Management - JAMS now predicts whether Jobs will miss their deadlines while there is still time to act. A new SLA Risk dashboard explains the reason for each prediction. It also maps the dependency chain behind each at-risk Job and notifies you when a Job’s risk status changes. JAX can help you investigate and respond.
Scheduler Health - JAMS now detects when the Scheduler has stopped doing its job even though its services look healthy. Examples include a schedule that is not being extended or Jobs that are overdue to start. Alerts appear in the new Notification Centre, and JAX can help you diagnose the cause.
Monitor Flow Visualization - A new Flow view on the Monitor shows active Monitor entries and their dependencies as a live graph. A Job Flow view shows the flow for a single Job. You can run any Monitor action from any node in the graph.
Universal Search - Find what you need from one search box. It searches Jobs, Folders, Variables, Credentials, Agents, Connection Store items, Queues, and Execution Methods.
Import and Export - You can now export object definitions to a bundle and import bundles from the Web Client, the Desktop Client, or Export-JAMSXml.
Workflow Job Viewer - View Workflow (WWF) Jobs in a visual designer, right in the Web Client.
Audit Trail - Every change to Jobs and Folders is tracked. You can browse revisions, compare versions side by side, and revert to an earlier version in one click.
Projected Schedules - The Job Summary pages now show past runs and predict upcoming runs on one timeline. The Job Summary page also includes a 7-day run history.
New Home Page - A new Home page brings together Quick Actions, Resource Documents, and a live Happening Now summary of the Monitor.
Cross-Domain Active Directory - Access and Security settings now follow Active Directory trusts and nested groups across domains, matching the Desktop Client. User Federations also add group synchronization and a Test Connection option.
ADFS Sign-In - ADFS is now a supported Identity Provider (SAML 2.0). It supports IdP-initiated sign-on, Windows SID identity mapping, and group names resolved through Directory Sync.
System API Tokens Expanded - API tokens can now be restricted to specific IPv4 ranges (CIDR), including behind a load balancer. You can also revoke or regenerate a token, and JAMS revokes tokens automatically when their Run As user is deleted.
A New Way to Work with Jobs - The Jobs page has been completely redesigned around how you find and manage Jobs. The new All Jobs view shows every Job in a single list that you can search and sort, with no need to drill through the folder structure. If you organize your work by folder and prefer to work that way, the folder view is still available. A My Favorites tab keeps the Jobs you use most one click away. To add a Job, mark it as a favorite from its edit page. A new Templates tab shows a card for each Execution Method. Click a card to open the Job Add drawer with that Execution Method already selected.
My Profile - The account menu now shows who you are logged in as and whether you’re a User or an Administrator. It also shows what kind of account you signed in with: a local JAMS account, your Active Directory through a User Federation, or an Identity Provider such as Entra ID, Okta, or ADFS. The new My Profile page displays your name, email, username, user type, and last sign-in. It also shows which directory or Identity Provider your account comes from, so you know whether to update your details there or ask your JAMS administrator. It also lists the API tokens tied to your account.
Live Dependency View - The Job Dependency View now shows live Monitor status for each node, and you can hover over a node to see its details.
JAX AI Agent
JAX Can Make Changes - JAX can now act as well as answer. It can create Jobs, manage triggers, dependencies, time windows, event handlers, and reports, enable or disable Jobs, reset triggers, and update parameters. JAX shows you each change and waits for your approval before applying it.
Contact Support from JAX - Open a support ticket without leaving the conversation. JAX writes a ticket summary from your chat, which you can edit before sending it to JAMS Support.
Scheduler and Integrations
Remote File Trigger - Start Jobs automatically when files arrive in Azure Blob Storage or Amazon S3. You can configure it on Job, Folder, and Monitor Entry schedules in the Web Client and through the REST API.
REST Execution Method - Call REST endpoints from a Job without writing scripts. It supports custom headers and request bodies, parameter substitution, and Basic, API Key, Bearer, and OAuth 2.0 Client Credentials authentication. A new REST Connection type stores your connection details. Configure REST Jobs in the Web Client.
Group Managed Service Accounts (gMSA) - Jobs can now run under a gMSA through the new Group Managed Service Account secret provider. You no longer need to store and rotate passwords for those Jobs. It is available in the Desktop Client and the Web Client.
Kerberos Support - JAMS now fully supports environments that allow only Kerberos authentication, including a Kerberos option in Agent Interactive Server setup.
AzureVM Execution Method - Start, stop, reboot, and delete Azure Virtual Machines from a JAMS Job, and cancel those operations. A new Azure VM Connection Store item stores your connection details. It is available in both the Desktop and Web Client.
Agents
FTPS for z/OS - z/OS Jobs now support FTPS, so file transfers to and from the mainframe are encrypted.
Enhancements
Web Client
More Execution Methods - You can now edit Automate, Banner, BannerProcedure, BannerWin, GoAnywhere, SAPV2, SQL Agent, SSIS Direct, and SSRS Jobs in the Web Client.
More Schedule Types - Job and Folder schedules now support Runaway, Short, and Stalled schedules, Send Email schedules, Notification Jobs, Recovery Jobs, Email Reports, and SSRS Print Reports.
Richer Monitor Details - Monitor Details add Schedules, Statistics, Entry Audit Trail, Impacted Jobs, and Documentation tabs, all with a consistent layout. The Monitor also has a new Description column. You can now download log files from the Monitor and History.
Smarter Query Management - The Future and Past Window filters have been reworked and filters are simpler to edit. A default query now runs automatically, and example queries are included to get you started.
Live Status for Agents, Queues, and Resources - Agents, Batch Queues, and Resources now show live values from the Scheduler, such as Agent state, Job counts, and Resource usage.
Sequence Task Bindings - Sequences now support Task Bindings, and the Sequence toolbox includes a Job selector.
Azure Key Vault Credentials - Credentials in the Web Client can now use Azure Key Vault as a secret provider.
SAP in the Web Client - SAP connections now run on .NET Core, so you can work with SAP Jobs in the Web Client.
Usability Improvements - The Web Client has been refined throughout:
Drawers for creating objects work the same way everywhere.
The breadcrumb bar shows when an object was last changed.
Summary tabs include an Inherited Configurations block.
Properties pages have new layouts.
Job Definition tabs can open in a full window.
Grids are standardized.
Desktop Client and Agents
TLS 1.3 Support - TLS 1.3 and a new TLS Safe option are now available wherever TLS 1.2 was offered.
Integrations
Informatica Cloud JWT Sessions - The Informatica Cloud integration now supports JWT-based sessions.
AWS SDK v4 - The AWS integrations now use AWS SDK version 4.
REST API
API Versioning - The JAMS REST API is now versioned, so we can add features without breaking your existing integrations.
API Token Diagnostics - The API log now includes more detail to help you troubleshoot System API Tokens.
Updated Components
Updated DevExpress to version 26, Rebex to R8. Also updated other third-party components to the latest and greatest.
In-product documentation links now point to docs.jamsscheduler.com.
Fixes
Scheduler
Resolved an issue where Jobs submitted with Submit-JAMSEntry -DependsOn were not released after a server reboot.
Resolved an issue where Jobs with more than one Recurrence enabled could start several new Jobs each time they completed. JAMS now uses only the next scheduled Recurrence.
Resolved an issue where a Notification Job set to run on Error did not run for Interval Trigger Jobs without Always Resubmit selected.
Resolved an issue where Job logs containing bare line feeds, such as some Banner Job logs, were not attached to notification emails.
Resolved an issue where date parameters were evaluated in UTC instead of local time when a Resubmit Trigger resubmitted a Job.
Resolved an issue where sending email through the Microsoft Graph API could block other Scheduler processing.
Resolved an issue where Send Email schedule items with a specific Mail Server selected did not send.
Resolved an issue where the Properties collection was missing from dynamic events.
Reduced repeated connection errors in the JAMSServer log on both failover and non-failover systems.
Schedule Trigger properties now display consistently with Mail Trigger and Group Behavior properties.
Agents
Resolved an issue where long IBM i Job logs displayed pages out of order in Show Details.
Resolved an object reference error in Agent Interactive when the remote host closed the connection.
Installer
Resolved an issue where JAMS services failed to start when the SQL Server password contained special characters such as {, >, or =.
Resolved an issue where updating the Web Client removed the JAMS API service.
Resolved an issue where the installer window did not open on some systems.
Desktop Client
Resolved loading issues when Windows uses non-English regional settings.
Resolved an issue where History entries were missing or out of place for Interval Trigger Jobs, including their Notification and Recovery Jobs.
Resolved an issue where problem reports could not be submitted from the Support dialog.
Resolved an issue where a Credential with an empty logon username prevented the Credentials page from loading.
Corrected the email address tooltips to explain that the Default Notify E-mail Address is always included in notifications and cannot be excluded with ‑*.
PowerShell
Resolved an issue where Get-JAMSAgent returned the wrong Agent state.
SQL
Resolved an issue where SQL Stored Procedure Jobs did not show schemas in the Database list or quote the connection string correctly.
Credentials
Resolved an issue where errors were logged when a non-administrator loaded Credentials that use a secret provider.


