Feature Updates
- Routines now run as their owners, and generated artifacts and run conversations belong to those owners. Publishing, activating, or running an inactive Routine may transfer ownership to the user performing the action; sandbox resources, credentials, and quotas remain bound to the Routine.
- Routine members with read access can view run conversations, but only the current owner can continue, stop, rename, or archive them. Both the previous and new owners are notified when ownership changes.
Bug Fixes & Improvements
- After the first message is sent, new conversations immediately appear in the sidebar and receive focus, do not appear twice when updated to their assigned names, and remain visible during page navigation.
- The title, action buttons, and table columns on the personal access token page now stay correctly positioned while scrolling. Tab spacing and the mobile scrolling experience have also been improved.
- The Scraper submenu now closes automatically when scrolling the platform list, preventing the floating menu from becoming detached from its original position or being positioned incorrectly.
- Artifact cards now have more consistent loading placeholders, clearer metadata placement, and improved menus and sharing indicators.
- Fixed an issue that prevented users with the appropriate access permissions from opening artifacts created by Routines.
- Improved batch record update performance, especially for large-scale updates involving many fields, while preserving response completeness, field and record order, permissions, undo, rollback, and API compatibility.
- Fixed an issue when importing App Builder projects containing named queries via GitHub pushes: outdated autogenerated query files are now refreshed and synced back to GitHub. Manually modified autogenerated files are still rejected.
- Changing or removing an App’s custom domain now releases the previous domain so it can be assigned to another App without conflict errors.