Product Update - v26.15
Details of the product update v26.15 from the 9th of April 2026.
New Features
New UI for Contract Messages Usage report page
Implemented separate message quota report for contracts and workspaces, common quota report refactored to use type (memory/messages) with different routes, APIs, and formatters.


Introduce new API endpoints for new quota type messages-quota-usages
See API documentation.
Implemented an automatic reset of the 2FA code fields after the first failed attempt. The system clears all inputs and return the focus to the first field to prevent redundant requests and accidental lockouts.
Add team/repo:function to the mapper step on execution page
Platform displays jsonataMap under the component/step

Enable Subscribe to errors by default for the flow creator in cases: copy flow, export flow, activate recipe
User automatically subscribes to flow’s errors after next actions:
- Copy flow
- Copy many flows
- Activate recipe
Syntax improvements for JSONata mode
We made general improving for syntax errors highlighting in JSONata mode
The “Show password” button on the “Profile Information” page
Added a “Show password” button to:
- Current password
- Change password
- Repeat new password

Fixed Bugs
- FIXED incorrect timestamp in the error notification
- FIXED error details not being available on the Thread Error page
- FIXED a bug where the browser’s “back” button worked only once and did not allow further navigation through browsing history on the Flow page
- FIXED quota exhaustion notification templates for non-80% thresholds and clarified message-count vs CPU/MEM wording
- FIXED an issue where the Memory Usage History diagram displayed
-1.024 KB for contracts with unlimited quota
- FIXED an issue where message-count monthly usage was not reset for workspaces and contracts without active flows at the beginning of the month
- FIXED an error where the “Something is technically wrong.” page appeared on the Contract Quota Usages page when usages were not found for
per_contract_container_count_limit and per_contract_message_count_limit
- FIXED a “Component not found” error when clicking the Back button in the Developer Team section
- FIXED a bug where the cursor jumped to the first position when manually typing data into input fields for mapping, sample, config, and retry
- FIXED a bug where variable fields were not required or validated on the recipe activation page (frontend validation added)
- FIXED a bug where the platform UI crashes when switching between REST API configurations
- FIXED an issue where the “Verify” and “Save” buttons remained active for “Basic Auth” or “API Key Auth” types without required credentials filled in
Components
- Initial component release
- ADDED
Make Raw Request action
- Initial component release
- ADDED
Add details to the Asset action
- ADDED
Assign Asset to the Category action
- ADDED
Create a Direct Link action
- ADDED
Finalize Upload action
- ADDED
Make Raw Request action
- ADDED
Request Upload URL action
- ADDED
Retrieve all Assets (with detailed info) action
- ADDED
Retrieve an Asset action
- ADDED
Retrieve Assets with Search Criteria action
- ADDED
Retrieve Direct Links action
- ADDED
Upload and Create Asset action
- ADDED
Upload the file action
- ADDED
Execute SuiteQL Query action
- ADDED
Request Headers parameter to Make Raw Request action
- UPDATED
elasticio-sailor-nodejs version to 2.7.8
- UPDATED dependencies
- REMOVED unnecessary dependencies
- ADDED support for the new authentication method -
Client credentials grant
- UPDATED
io.elastic:sailor-jvm version to 5.0.1 to address the issue when the component failed to execute when there was an array in any of the preceding steps passthrough data
- FIXED issue in the
Select trigger
- IMPROVED
Select trigger: support case-insensitive %%EIO_LAST_POLL%% placeholder, handle quoted placeholders, and support date-only/high-precision polling values.
- FIXED issue in the
Get Rows Polling trigger
- IMPROVED Date/Timestamp parsing in
Get Rows Polling trigger to support fractional seconds (up to 9 digits) and date-only formats (e.g., YYYY-MM-DD).
- IMPROVED snapshot accuracy and safety by using direct
ResultSet.getTimestamp() access, preventing string-parsing errors during polling.
- FIXED MySQL timestamp comparison in polling trigger by using CONVERT(?, DATETIME(3)) for exact precision matching.
- FIXED JsonObjectBuilder reuse bug in getRowsExecutePolling method to prevent data corruption.
- FIXED maxPollingValue initialization in
Get Rows Polling trigger to ensure accurate snapshot updates.
- FIXED
Get Rows Polling trigger now correctly defaults to Unix Epoch (1970-01-01) for the first execution.
- UPDATED
Select trigger documentation to clarify that it defaults to today’s midnight.
- IMPROVED unit test cases to verify trigger fallback behaviors for missing or invalid inputs.
- FIXED incorrect SQL Parameter Binding Order in NewSelectAction
- FIXED certificate error in
Subscribe to platform events trigger
- REMOVED legacy
elasticio-node dependency and transitioned to local utilities
- UPDATED Node.js engine to 24.x
- UPDATED
elasticio-sailor-nodejs version to 2.7.8
- FIXED
ClassCastException in MessageResolverImpl when message body was a JSON array, and gracefully handle missing or null message bodies