2026.4 Release Notes

Release Highlights

  • OCLI for multitenant customers is now available for licensed users according to permissions that are defined by new roles. See the Profile Page documentation for more information.

  • A filter bar has been added to the Jobs and Packages tabs on the Floe page and to the Scaling Groups and Users tabs on the Systems page. You can filter by name, ID, and other attributes. Several filters may be applied at the same time.

User Interface Notes

Home Page

  • A “Create Project” button has been added back to the Home page.

Active Data Bar

  • It is now possible to download records from the Records Filter drop-downs on the Active Data Bar.

System Page

  • A Services tab has been added to the Systems page. You can start, stop, share, unshare, and delete services from this tab.

  • Scaling groups can now be arranged by instance families. A toggle allows you to group by family prefix.

  • The full group name can be copied for each instance group using the copy icon next to the name.

Floe Page

  • From both the Workfloes and Jobs tabs, users can now navigate to the Packages tab with only the source package showing.

Jobs Tab

  • A new button on the Parameters panel in the detailed job information allows you to download the job parameters as a JSON file.

  • Right-clicking on the dataset ID link in the Job input parameters now allows for copying the link and opening in a new tab, window, or split.

Molecule Search Page

  • Admins can now see, load, unload, and delete all custom databases for their organization.

Bug Fixes

  • Open-ended range values are now sorted correctly in the spreadsheet.

  • On a trackpad, swiping left to scroll left in the spreadsheet could inadvertently trigger a back action and take you off the 3D & Analyze page. This issue has been fixed.

  • A bug in the Filter Collection Floe had caused the output collection file to show no data. This was especially pronounced for collections with a large number of shards. The issue has been fixed.

  • On the Data page, it is now easier to shift-click to select multiple items in a folder. Previously, only a small section of the row allowed selection of that row, but it is now possible to click anywhere in the row that is not a button.

  • An issue has been fixed where clicking an input parameter link in the Parameters panel of the Jobs tab could display unrelated resources when IDs overlapped across types. Incorrect filter settings could also lead to seeing NO results. The link now filters by the correct resource type.

  • A bug has been fixed where deleted users were not being removed from the Users tab of the Systems page. Only admins can see the role and status of other users.

  • An issue has been fixed where a higher number of rotatable bonds sometimes appeared in the spreadsheet as a result of the inclusion of aliphatic rings in rotatable bond counts.

Orion Back End Notes

Note

Orion backend and other Orion changes of interest to all users are listed in this section of this manual. Orion Platform changes of interest to Python programmers are summarized in the Orion Programming Guide release notes.

  • By default, tokens will now expire approximately 90 days after creation; users will be notified by email seven days before token expiration. If tokens are expiring soon, a dismissable notification will also appear on login with an option to link to manage tokens. These settings are configurable for your organization. For help with changing them, please contact your account manager. For tokens that were created prior to the 2026.4 deployment, the 90 days will start from the date of deployment and NOT the token creation date. The token expiration date can be found on the Token tab of the user’s Profile page.

  • A bug has been fixed that could cause some Orion job logs to be incomplete, with some debug or error messages missing even though the operations ran successfully.

  • An issue has been fixed where scheduler restarts or connectivity disruptions resulted in very large jobs having more retries.

  • When a user is deleted, any service specs they own are preserved and automatically transferred to a new owner, and the name of each transferred service definition is appended with a “from username” suffix. All active running instances are safely terminated rather than left running unattended.

  • Molecule Search 3D custom databases can avoid being backlogged by pinning the instance type to limit the compatible instances and avoid unexpected charges.

Information for Programmers

Note

The Programming Guide covers only Orion Platform.

Managed Service customers can use the Orion Platform interfaces to develop their own cubes and floes for execution in Orion. They can use the Orion Command Line Interface (OCLI) to execute operations using the Orion Client facilities. They can also develop and manage Molecule Search databases. For more information, see the Programming Guide.