OpCon Release Notes
ResourceMonitor
21.1.0
Bug Fix
✅ Log-archive retention now respects the INI file: The ArchiveDaysToKeep setting configured in the INI file is now applied correctly at service startup. In prior releases this value was ignored and the default retention was used instead.
21.0.0
FIPS Compliance & .NET Framework 4.8.1
✳️ ResourceMonitor has been updated to be FIPS-compliant and now runs on .NET Framework 4.8.1. Both the service and the UI have been rebuilt against the latest FIPS-compliant SMA libraries, and the installer automatically deploys the .NET Framework 4.8.1 runtime as a prerequisite where it is not already present.
Other Improvements
✳️ Service startup and logging-initialization errors are now written to the Windows Event Log, making installation and configuration issues easier to diagnose.
✳️ Improved service responsiveness and a cleaner, faster service shutdown.
Winter 26
26.0.2
NOTE: Verify/Upgrade these components if applicable:
- Enterprise Manager - 26.0
- ServiceNow Connector – 21.4 or higher
- WebServices Connector – 21.2 or higher
- Deploy – 26.0.0 or higher
- Relay - 25.1.1 or higher
2026 March
Server
✅ OC-5055: Truncated SQL query in SAM and Critical logs to avoid overflow.
✅ OC-6340: Fixed an issue where the Reporting Service could crash on DST spring‑forward transition days for environments using a US (or similar) timezone with the default schedule time of 02:00.
REST API
✅ OC-6104: Added support for a MaxPoolSize configuration key in the API, allowing administrators to specify the maximum connection pool size via SMAODBCConfiguration.DAT.
26.0.1
NOTE: Verify/Upgrade these components if applicable:
- Enterprise Manager - 26.0
- ServiceNow Connector – 21.4 or higher
- WebServices Connector – 21.2 or higher
- Deploy – 26.0.0 or higher
- Relay - 25.1.1 or higher
2026 February
OpCon Release 26 -- What's New
Summary
Release 26 focuses on better visibility, stronger reliability, and a more unified user experience while ensuring existing automations continue to run without disruption.
Reporting & Audit Enhancements
What's New
✳️ OC-5315, OC-3212: Expanded Reporting Capabilities New reports and enhancements provide deeper insight into system activity and performance, helping teams monitor operations more effectively.
✳️ OC-3212: Comparative Job Execution Statistics Report A new report enables side‑by‑side analysis of job execution statistics to identify trends and performance changes over time.
✳️ OC-5315: Improved Date Filtering & Report Layouts Reports now support clearer date ranges and additional columns, making it easier to filter and analyze results.
✳️ OC-5319: Direct Access to Report Logs Report logs are now visible directly within Solution Manager for on‑prem customers, improving troubleshooting and transparency.
✳️ OC-5323: Tracked Changes to Report Settings All report configuration changes are now recorded in an audit table, providing greater visibility and auditability.
✳️ OC-5287: New Reporting Configuration UI A dedicated Reporting tab has been added to Server Options, centralizing reporting configuration in one place.
✳️ OC-5867: Improved Reporting Security Reporting database connections exposed through the REST API on Windows now support encryption for stronger data protection.
Why This Matters
Customers gain clearer insight into automation performance, better auditability, and faster issue resolution without manual data extraction or external tooling.
Solution Manager Improvements
What's New
✳️ OC-5051: Updated Deploy Server Log and ImpEx2 Log Deploy server logs and ImpEx2 logs (now renamed to SMAImpEx2.log) are now visible in the Solution Manager Logs page, improving consistency and simplifying diagnostics.
✳️ OC-5336: Updated Runtime for Core Server The OpCon core server has been upgraded to run on the latest .NET 10 runtime, improving performance, stability, and long‑term supportability.
✳️ OC-5902: Enhanced Logging Alignment ReportingService logging now aligns with standard OpCon conventions, improving consistency and simplifying diagnostics.
Visibility Improvements Across Reports Column ordering is retained during report interactions; filters now adhere to industry standard best practices for ease of use, and downloads now include all pages, not just the current view.
Why This Matters
These updates improve reliability and reduce friction when monitoring and managing automation at scale.
Studio & Workflow Builder Usability Fixes
What's New
✳️ OC-5902: Improved Job Editing Experience Editing existing jobs no longer resets node positions, preserving workflow layouts.
✅ OC-4541: More Reliable Dependency Creation Validation errors when creating dependencies via drag‑and‑drop have been resolved.
✅ OC-4140: Improved Workflow Navigation Issues where jobs disappeared from the canvas but remained visible in the mini‑map have been fixed.
✅ OC-4365: Faster, More Predictable Interactions Lag between job selection and toolbar actions has been eliminated, ensuring actions always apply to the correct job.
✅ OC-4537: Enhanced Script Editor Search CTRL+F now reliably opens the script editor's internal search, regardless of Caps Lock status.
Why This Matters
Workflow creation and maintenance is faster, more predictable, and less error‑prone, especially for complex job flows.
NetCom / Relay Reliability & Monitoring
What's New
✳️ OC-5885: Smarter Message Cleanup & Processing Message deletion logic has been corrected to use true message ID boundaries, preventing accidental deletion of unread or newly inserted messages.
✳️ OC-5885: Automatic Cleanup of Stale Messages Stale TX2 messages are automatically removed on startup and when agents reconnect, reducing backlog issues.
✳️ OC-5885: Duplicate Message Prevention Duplicate messages that accumulated during downtime are now detected and skipped.
✳️ OC-5885: New Message Buildup Monitor A new monitoring system automatically detects when messages accumulate in the database or in‑memory queues.
✳️ OC-5885: Automatic Recovery Actions When buildup is detected, connections are automatically reset to restore normal processing.
✳️ OC-5885: Enhanced Debugging & Visibility Detailed message ID logging improves troubleshooting and visibility into message flow and processing.
Why This Matters
Customers benefit from improved resilience, faster recovery from network issues, and significantly reduced risk of message backlog or loss.
Security & API Updates
What's New
✅ OC-4593: REST API Security Hardening A path traversal vulnerability in the Logs endpoint has been addressed, strengthening overall API security.
✅ OC-5089: Updated API Documentation Job History API documentation has been updated to reflect current behavior and improve developer usability.
Why This Matters
These changes improve security posture while making integrations easier to build and maintain.
Unified Branding & Modernized Experience
What's New
✳️ OC-2515: Consistent OpCon Branding Solution Manager has been visually updated to align with the broader OpCon and Continuous brand guidelines.
Standardized Layouts & Interactions Features now follow consistent visual and interaction patterns, improving usability and reducing cognitive load.
Why This Matters
A cleaner, more consistent experience makes OpCon easier to learn, faster to use, and more intuitive across teams.
Fall 25 - Fix
25.3.1
NOTE: Verify/Upgrade these components if applicable:
- Enterprise Manager - 25.0
- ServiceNow Connector – 21.4 or higher
- WebServices Connector – 21.2 or higher
- Deploy – 25.3.0 or higher
- Relay - 25.1.1 or higher
2025 December
Server
✅ OC-5355: Fixed an issue with $JOB:ADD events.
Fall 25
25.3.0
NOTE: Verify/Upgrade these components if applicable:
- Enterprise Manager - 25.0
- ServiceNow Connector – 21.4 or higher
- WebServices Connector – 21.2 or higher
- Deploy – 25.3.0 or higher
- Relay - 25.1.1 or higher
2025 November
Installation
✅ OC-4388: Fixed an issue where generated BIRT reports were blank due to a missing jtds-1.2.8.jar.
Server
✅ OC-3549: Fixed an issue where SAM allowed empty instance properties when an external event had extraneous semi-colons in the instance property parameter.
✅ OC-4607: Request Router now handles database connection loss during initialization or request cleanup without halting request processing or flooding logs with repeated errors.
Solution Manager
✳️ OC-2081: OpCon now employs standard password salting and hashing techniques to ensure the secure storage of user passwords. This enhancement allows users to create passwords that exceed the previous 12-character limit, offering greater flexibility and security. However, please note that for backward compatibility, the ImpEx user must continue to use passwords that are 12 characters or fewer to ensure proper functionality.
✳️ OC-2628: An Annual Plan By Calendar Dates Report is now available in the Reporting Library. This report shows all defined dates on user-defined calendars.
✳️ OC-2629: A Cross Reference Schedules and Jobs Report is now available in the Reporting Library. This report shows all jobs and their associated schedules.
✳️ OC-2630: A Current Global Properties Report is now available in the Reporting Library. This report shows current values of global properties.
✳️ OC-2631: A Current Threshold Values Report is now available in the Reporting Library. This report shows current threshold values and descriptions.
✳️ OC-2632: A Current Resource Values Report is now available in the Reporting Library. This report shows current resource values and descriptions.
✳️ OC-2638: A Frequencies and Associated Jobs Report is now available in the Reporting Library. This report shows all frequencies and their associated jobs.
✳️ OC-3715: The Job Execution History page has been significantly optimized for faster load times and improved responsiveness.
✅ OC-3020: Fixed an issue where certain filters did not work when language was set to French.
✅ OC-3610: Fixed an issue where updating a batch user removed them from the daily job.
✅ OC-3611: Fixed an issue where instance properties were removed from the master schedule when the schedule was changed to multi-instance.
✅ OC-3639: Fixed an issue where the URL to fetch daily jobs was longer than allowable by the browser.
✅ OC-3666: Fixed an issue where migration item value in Service Requests did not display correctly for regex.
✅ OC-3745: Fixed an issue where secondary settings for Customer Secret (Email and SMS) under Server Options were not cleared when the associated primary setting was deleted.
✅ OC-3779: Fixed an issue where cross-references were not detected when the job name contained an underscore.
✅ OC-3793: Fixed an issue where fetching reports timed out and returned an error.
✅ OC-3962: Fixed an issue where machine cross-references was empty.
✅ OC-3981: Fixed an issue where the agent's properties were not visible when the agent was communicating.
✅ OC-4145: Fixed an issue where the schedule name was not filled in when adding a job from the Studio page.
✅ OC-4625: Fixed an issue on the Master Jobs page where a "Job not found" error appeared after a job was renamed and the user navigated back using the browser’s back button.
✅ OC-4653: Fetching job execution history from the Master Jobs page now returns the correct job history.
✅ OC-4812: Fixed an issue where OpCon roles were missing in SSO group mappings.
✅ OC-4998: Added proper error handling for cases where a job cannot be found and introduced a loading state while job details are being fetched.
✅ OC-5000: Resolved an issue in the Vision Health dashboard where graphs failed to display on initial load.
REST API
✅ OC-45: Fixed an issue where <reqparams> values were missing in the API request which caused "Output not found" in Solution Manager when viewing SAP BW or SQL job output.
✅ OC-2883: The api/jobHistories endpoint now returns only the matching jobs when both "scheduleId" and "jobName" are specified.
✅ OC-4261: Resolved an issue where heavy REST API usage could exhaust the SQL connection pool, causing Solution Manager to become unresponsive.
ImpEx2 Web Service
✅ OC-1906:
- Fixed a problem during Schedule Import using Deploy when schedule instance properties are merged if Deploy rule 'Update Schedule Instance Properties Allowed' is not selected
- Implemented additional Deploy rule 'Merge Schedule Instance properties'. By default, no changes are made to Schedule Instance properties
- If Deploy rule 'Update Schedule Instance Properties Allowed' is not selected and Deploy rule 'Merge Schedule Instance properties' is selected the schedule instance properties will be merged
✅ OC-3092: Fixed a problem when performing script runner match. Removed CommandFormat match as runner name and platform id provide the required information.
✅ OC-3683: Fixed a problem when retrieving batch user definition from the database and the batch user name contains a special character ([,.).
Documentation
✅ OC-3902: Corrected API Swagger documentation for api/propertyExpression.
Summer 25
25.2.0
NOTE: Verify/Upgrade these components if applicable:
- Enterprise Manager - 25.0
- ServiceNow Connector – 21.4 or higher
- WebServices Connector – 21.2 or higher
- Deploy – 25.0.0 or higher
- Relay - 25.1.1 or higher
2025 July
Relay
✅ OC-3600: Fixed an issue where Machines may be placed offline by NetCom/Relay after an interruption to communication.
Solution Manager
✅ OC-52: Fixed an issue where the time 12:00 PM is displayed as 0:00 PM in Solution Manager Studio when editing frequency values on a job.
✅ OC-30: Fixed an issue where users were unable to add frequency to a multi-instance schedule.
✅ OC-12: Fixed an issue where user could not view log page unless they have both View App logs and View Schedule Build log permission.
✅ OC-351: Fixed an issue where Frequencies cross references were not working when the name contains "/".
✅ OC-2795: Fixed an issue where jobs with dependencies and a start offset time displayed incorrect start times.
✅ OC-1826: Resolved an issue where filtering agents by type returned no results for ACS and RPA agents.
✅ OC-2168: Fixed an issue where long response time was causing a timeout when loading history.
✅ OC-2837: Fixed an issue where a user could not update Jobs in admin mode immediately after creating one without refreshing the application.
✅ OC-2881: Fixed an issue causing insufficient space to fill in recurring instance data in the 'When Jobs Finishes OK' section of a daily job's frequency. Additionally, fixed an issue where the 'Resulting Date/Time' was made a required Date/Time picker field in the 'When Job Finishes OK' section for 'Run Again' with 'Recurring Instances'.
✅ OC-2891: Resolved an issue where the frequency list for a master job was not populated when adding a dependency to a master job in Studio.
✅ OC-3016: Removed Maintain Frequencies option as it was not being used by any function privileges.
✅ OC-3022: Fixed an issue in Studio where the View button was incorrectly enabled when it should have been disabled.
✅ OC-3152: Fixed an issue where it was not possible to update an encrypted Global Property in the Solution Manager if you don't know the original value of the Global Property.
✅ OC-3253: Fixed an issue where used trigger names become unavailable across all groups.
✅ OC-3268: Fixed an issue where SQL Job Types created in Solution Manager did not store batch user information correctly, causing jobs to fail to start.
✅ OC-3284: Improved error messaging in the Batch Users API for cases where the platform or platform ID is null in POST and PUT requests.
✅ OC-3366: Fixed an issue where SQL database scripts included an extra character on the GO line, which could cause execution errors during deployment.
✅ OC-3620: Fixed an issue in Schedule Build, where a schedule is selected after selecting the date and other build options, the selections shown in the UI are ignored and it attempts to build the schedule for the current date.
Spring 25
25.1.3
NOTE: Verify/Upgrade these components if applicable:
- Enterprise Manager - 25.0
- ServiceNow Connector – 21.4 or higher
- WebServices Connector – 21.2 or higher
- Deploy – 25.0.0 or higher
- Relay - 25.1.1 or higher
2025 June
Relay
✅ OC-3600: Fixed issue where Machines may be placed offline by NetCom/Relay after an interruption to communication.
25.1.1
NOTE: Verify/Upgrade these components if applicable:
- Enterprise Manager - 25.0
- ServiceNow Connector – 21.4 or higher
- WebServices Connector – 21.2 or higher
- Deploy – 25.0.0 or higher
- Relay - 25.1.1 or higher
2025 June
Solution Manager
✳️ OC-2843/OC-2950: Added more resilience to scheduling message logic for guaranteed delivery. Also added some extra debug messages at Trace Level 1 to provide us more information in the logs in case the problem recurs in spite of improved logic.
✳️ OC-2911: Fixed job not found error "not valid".
Deploy
:eight_spoked_check_mark: OC-3092: Fixed a problem when performing script runner match. Removed CommandFormat match, as runner name and platform ID provide the required information.
NOTE: Verify/Upgrade these components if applicable:
- Enterprise Manager - 25.0
- ServiceNow Connector – 21.4 or higher
- WebServices Connector – 21.2 or higher
- Deploy – 25.0.0 or higher
- Relay - 25.1.1 or higher
2025 May
Server
✳️ OC-2186: Added OAuth support for SMTP notifications, replacing Basic SMTP (Exchange), which will be deprecated by Microsoft in September.
✅ INTPLT-492: ACS configurations generated over Relay will now have the correct version information populated. Users who wish to use ACS integrations over Relay that require data migrations should update to Relay 25.1.0.
✅ OC-3: Fixed an issue where the TLS Certificate Distinguished Name of Windows agents was overwritten when the agents disconnected and reconnected.
✅ OC-8: Fixed an issue where stopping SMA OpCon Service Manager service from services console, times out and says service did not respond to the start or control request in a timely fashion.
✅ OC-2760: Fixed RequestRouter to process schedule build and other requests targeted for it without getting stuck on unprocessed requests targeted for relay agents.
✅ OC-2843: Added more resilience to scheduling message logic for guaranteed delivery. Also added some extra debug messages at Trace Level 1 to provide more information in the logs in case the problem recurs in spite of improved logic.
✅ OC-3040: Allows integrations built on ACS to utilize Instance Properties when constructing log file paths.
✅ OC-3045: Enables job data cleanup on job deletion for jobs which ran on an Agent configured via Relay.
Solution Manager
✳️ OC-393: Accessibility support has been added to the main navigation, and the following Solution Manager pages: Job Execution History, Self-Service, Schedule Build, Daily Jobs, Batch Users, Notification Triggers, Master Jobs, to support WCAG accessibility standards.
✳️ OC-2082: A global property for Admins has been added to set the option retention policy on the Operations screen.
✳️ OC-2467: Added a new global setting in Server Options that completely turns Otto functionality off.
✳️ OC-2474: Additional fields added to the SMTP Server Options configuration for the chosen auth implementation.
✅ OC-6: Fixed an issue where clicking the [x] in the bottom bar on the Vision Health page does not de-select the selected cards.
✅ OC-15: Performance enhancements and error resolutions in Pert view where blank page or a timeout error occurred.
✅ OC-59: Fixed an issue where renaming a group in Notification Triggers was experiencing the cursor jumping to end of name after typing one character.
✅ OC-161: Fixed an issue where French translations were not applied on the Execution History view for Daily Jobs.
✅ OC-165: Fixed an issue where the User Input Caption value was cleared when changing the User Input Type when configuring User Inputs for a Service Request.
✅ OC-346: Fixed an issue where ACS daily jobs did not display the machine or machine group name.
✅ OC-347: Fixed an issue where the user was unable to update a Job Group after renaming a selected Job.
✅ OC-348: Fixed an issue where Requires XML Escape was not available for ACS master jobs.
✅ OC-350: Resolved an issue in Daily Jobs where the start Machine for File Transfer Jobs was not updated when the source machine changed.
✅ OC-353: Fixed an issue in Notification Triggers where typing a "/" in the job name field breaks functionality.
✅ OC-354: Fixed an issue in Solution Manager where the ability to translate an event from Enterprise Manager was not working.
✅ OC-2086: Fixed an issue where clicking cancel in the Configure Jobs Dialog in daily job processes page will cause page to crash.
✅ OC-2115: Fixed an issue where editing the Daily Job through Solution Manager was resetting all restart data.
✅ OC-2117: When opening the daily job right panel, if a current step is defined, it now pre-populates the “Choose a step” field and enables the “Restart on step” button by default.
✅ OC-2119: Fixed an issue with default values in the JCL Access dialog for z/Os jobs.
✅ OC-2137: Fixed an issue where nodes in Studio were remaining stacked on top of each other.
✅ OC-2181: Refined some of the navigation issues to limit the amount of clicks users need to take to navigate through the application.
✅ OC-2183: Removed Back buttons from various pages to encourage the use of standard browser back and forward capabilities.
✅ OC-2898: Fixed an issue where clicking on the processes filter loads a blank page.
✅ OC-3024: Fixed an issue where multiple Access Codes could not be deleted.
✅ OC-3038: Fixed an issue where some RPA jobs could not be displayed due to unexpected Instance Properties values.
✅ OC-3042: Fixed a rendering issue which could sometimes prevent selection of agents for Master Jobs that run on ACS Integrations.
REST API
✅ OC-1837: When sending password resets, additional logging in the notify handler has been added when the api requests the password reset endpoint.
✅ OC-1894: Fixed an issue where Jobs submitted were not the correct ones.
✅ OC-2127: Updated value for SMACDBUILD_VER for 25.1.0.
✅ OC-2623: Fixed an issue where the OpCon version was not updated properly in the database.
✅ OC-2665: Fixed an issue in the PUT and POST machines API when providing machine group(s)
ImpEx2 Web Service
✅ OC-137: Update ImpEx2 to support RPA agent
✅ OC-325: Updated Deploy and ImpEx2 to include the capability to move RPA tasks between systems.
✅ OC-2578: Fixed a problem in ImpEx2 during workflow deployment when a resource or threshold name contains a period (.) causing deployment failure.
✅ OC-2889: Included Deploy 'Frequency_Use_Existing_Definitions' transformation rule capabilities that uses an existing frequency definition when the target job exists.
✅ OC-3092: Fixed a problem when performing script runner match. Removed CommandFormat match as runner name and platform id provide the required information.
Winter 25
NOTE: Verify/Upgrade these components if applicable:
- Enterprise Manager - 25.0
- ServiceNow Connector – 21.4 or higher
- WebServices Connector – 21.2 or higher
- Deploy – 25.0.0 or higher
- Relay - 24.3.2 or higher
2025 March
Server
✳️ OPCON-25853: Upgraded OpCon to .NET 9.
✅ OC-2499: Fixed database re-connection logic to prevent NotifyHandler from hanging during database disruptions.
✅ OC-2502: Providing a delayed start and checking for certificate file in NetcomApi to prevent errors encountered during initialization of service.
✅ OPCON-21285: Fixed an issue where the start time of a job that depended on a container job in the parent schedule was incorrect.
✅ OPCON-23582: Fixed an issue where the estimated start time of a job was incorrect when it depended on a job in a different schedule.
✅ OPCON-24595: Fixed an issue where SMANotifyHandler had its log locked, causing it to become unresponsive.
✅ OPCON-24956: Fixed NetCom deadlock which would prevent some Agent types from being marked down after failing heartbeats.
✅ OPCON-25930: Fixed a NetCom issue which caused some ACS jobs to fail on restart due to invalid references
✅ OPCON-25969: Fixed an issue which could cause ACS integrations to lose variable tokens used in job configurations after completion of a job run.
✅ OPCON-25982: Fixed an issue in NetCom where ACS job starts would sometimes request job status information even when the job had previously reported completion.
✅ OPCON-26144: Fixed an issue that caused the error "Adding the specified count to the semaphore would cause it to exceed its maximum count" when communication with an RPA agent was enabled.
✅ INTPLT-32: Fixed an issue where the customer was receiving an invalid URI and internal server error when authenticating machines.
Solution Manager
✳️ OPCON-23094: Added support for logs that aren't text and inclusive of video logs through the job output screen.
✳️ OPCON-23095: Licensing logic using the (new) agent ID being used for OpCon RPA is enforced.
✳️ OPCON-23096: Added OpCon RPA script runner & script type capabilities for Script Repo use.
✳️ OPCON-23373: Otto has learned a new skill! Users should now be able to ask Otto to retrieve a single log file by name.
✳️ OPCON-24552: Otto improvements from UAT including: improved formatting, improved date range options, a clear conversation action, and case insensitivity on requests.
✳️ OPCON-24683: Usage information, page count tracking, and click behavior tracking are captured.
✳️ OPCON-24689: Otto has learned a new skill! Users should now be able to ask Otto to summarize build results for a schedule on a specified date and return a link to the log details page directing users to the correct information if Otto is unable to create a summary.
✳️ OPCON-25940: Added an option in User Profile Settings page to uncheck selected jobs after job status update on the Processes page.
✳️ OPCON-25961: Added the ability to archive the output of an MFT Job.
✅ OPCON-19737: Fixed an issue where a machine's capabilities were not validated when it was added to a machine group.
✅ OPCON-23224: Fixed an issue where the user couldn't add jobs to daily multi-instance schedules.
✅ OPCON-24389: Fixed several issues related to the machine groups panel on the agents page.
- Fixed an issue where all machine groups start on the left even if agent has machine groups assigned
- Fixed an issue where agents page groups column is not updated after an update in the machine groups panel
- Fixed an issue where left and right arrows were enabled without any selected items
✅ OPCON-24390: Fixed an issue where the filtered agent status was not reflected properly in the url query parameter.
✅ OPCON-24394: Fixed an issue where clearing the machine group filter on the Agents Page did not restore those agents not in a group.
✅ OPCON-24405: Fixed an issue where the Logs API does not remove/archive application log files correctly.
✅ OPCON-24492: Fixed an issue where the default values were not the same when creating a new OpCon MFT agent.
✅ OPCON-24512: Fixed an issue where retry on failure values were removed after updating a daily job.
✅ OPCON-24563: Fixed an issue with 'View Service Requests' privilege that let the user see jobs that they did not permissions for.
✅ OPCON-24637: Fixed an issue where double quotes were mishandled in Episys Answer Prompt jobs.
✅ OPCON-24949: Fixed an issue causing agents page to timeout after selecting an agent.
✅ OPCON-25103: Fixed issue "Cannot Load Daily Jobs" when right clicking certain jobs in Operations page.
✅ OPCON-25111: Fixed an issue where a role could not be updated if a machine group to which it has access is deleted.
✅ OPCON-25150: Fixed an issue where filtering by column resets on every visit on the agents page.
✅ OPCON-25151: Resolved an issue where assigning 'Can Update' access to a resource for a role did not work as expected.
✅ OPCON-25158: Fixed an issue where 'Daily Job Frequency' offset values were cleared on second save via turning admin off.
✅ OPCON-25159: Fixed a permissions issue with master jobs where users with any privilege in <All Departments> were incorrectly able to modify master jobs.
✅ OPCON-25736: Fixed an issue which prevented users from selecting an ACS Integration as a Script Runner OS Type if the user had multiple ACS integrations installed.
✅ OPCON-25757: Fixed the error message "Trigger name is required” when clicking the Test button while creating a new notification trigger.
✅ OPCON-25786: Fixed an issue where the user could save a Daily Job while ACS was still loading the schema.
✅ OPCON-25790: Fixed an issue where the Otto chatbot lost chat history when the navigation button was used while already on the destination page. Now, the navigation button is hidden in this scenario to prevent unnecessary page reloads and ensure chat continuity.