Improved the flow name visibility in the filter dropdowns on the Executions, Containers, and Logs pages. 
Now, when hovering over flow names in the filter dropdowns, users can view the full flow name if it’s too long. This update facilitates better understanding and navigation within the platform, making it easier for users to identify and select specific flows for their tasks.
Experience increased productivity with the new bulk flow export capability on the platform. The new dropdown menu Exports now offers users two convenient options: Export Flow(s) and Export to a Recipe.
Selecting Export Flow(s), users can choose one or multiple flows and export them simultaneously to any available contract and workspace as flow drafts. This feature empowers users to efficiently manage and export multiple flows with ease, optimizing their workflow and boosting productivity.
label field displayEnhanced data representation in the JSONataView viewclass with the introduction of label field display. Users can now easily access and view the contents of the label field within JSONataView, as described in the component.json file. This enhancement allows for clearer data visualization and interpretation within the viewclass, and provides users with enabling better understanding and analysis of the label field content within the JSONataView viewclass.
With the new API endpoint https://api.elastic.io/docs/v2#/flows/delete_flows_subscription, users can now unsubscribe from flow errors across all their flows or specifically within a specific workspace. 
This feature empowers integrators to efficiently manage error notifications, providing flexibility and control over error subscriptions for enhanced workflow efficiency.
Default label display for Router component branchesUsers can now easily view the Default label associated with a branch of the router component directly on the flow queue page. 
This update provides users with quick access to essential information, facilitating better understanding and management of the routing logic within the flow queue.
429 for exceeded Webhook requests limitWhen the quota for Webhook requests is exceeded, the Webhook URL now responds with a 429 Too Many Requests status code.
Users interacting with the credential fields of the Webhook component will now go through validation to identify unsupported characters.
In case unsupported characters are detected, an error message displaying Disallowed symbol(s) will prompt users, ensuring data integrity and safeguarding against unauthorized access.
Note:
* Current whitelist for header-name looks like: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_. More info
* Current whitelist for header-values looks like: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_.~. More info
x-eio-signature will be used.Ordinary or Real-time) on the Activate Recipe action.Activate Recipe action.1.0.0Make Raw Request Action1.0.0Make Raw Request Action1.2.4Maester Object ID or the Maester Object URL as input in the Create Commit Action1.2.0Maximum response size in bytes configuration field to HTTP request Action1.5.0Re-assembled Message Action - now all messages are stored in memory within the component and saved to the external storage (Maester) only when neededEmit result as array to Re-assembled Message Action2.7.21.1.0Execute Mutation Action3.3.0Read CSV file from URL Trigger1.3.1Emit Behaviour select view to the Select Action1.0.12.7.22.0.8Could not parse Maester object as it is not a JSON object2.7.21.0.3Cannot read properties of undefined (reading 'data') in Trigger another flow Action2.7.2