Released: 2024-07-04
Improved filtering functionality on the Execution page with the addition of a checkbox option to hide executions without messages. Users can now easily toggle this feature next to the filters, effectively removing empty executions from view. This enhancement optimizes the display of relevant execution data, enabling users to focus on executions with messages and enhancing the overall usability of the Execution page for efficient flow monitoring and analysis.
Enhanced capabilities with the addition of handling for unprocessed expiration errors from Kubernetes. A dedicated metric that tracks and logs restarts associated with unprocessed expiration errors, providing valuable insights into system stability and performance.
The replacement of the old library with a new, more efficient one has significantly enhanced UI memory usage, resulting in a smoother experience when working with extensive sample datasets. This upgrade aims to provide users with a more responsive interface, eliminating freezes and ensuring a seamless workflow when handling large sample loads.
TypeError: Cannot read properties of undefined (reading 'filter') on the Flows page, even when no flows are present.io.elastic:sailor-jvm:4.0.2 has been released.1.0.0 (v24.27)Make Raw Request ActionWebhook Trigger1.0.0 (v24.27)Make Raw Request Action1.1.0 (v24.27)SASL/OAUTHBEARER1.1.0 (v24.27)Lookup by id checkbox to Trigger another flow ActionRetry errors checkbox to Trigger another flow ActionSocket Hang Up issue1.4.3 (v24.27)Consume trigger now locate the logs and messages in the last flow executionv2.7.2v0.10.41.1.0 (v24.27)Lookup Object By ID Action1.2.0 (v24.27)Webhook Trigger1.7.1 (v24.27)v2.7.2component-commons-library to v3.2.0Released: 2024-09-04
By increasing the allowable number of subdomain characters from 10 to 50, users now have greater flexibility when sending invites, accommodating longer and more diverse subdomain configurations. This enhancement simplifies the process of inviting new users and ensures that workspace invitations can accurately reflect the unique subdomains of each recipient, enhancing communication and user engagement within the workspace.
Profile Information page to React (v24.36)This update enhances the performance and responsiveness of the user profile display, offering a more intuitive and efficient way to manage and view profile details. The transition to React not only modernizes the user interface but also lays the foundation for future enhancements and optimizations, providing users with a more seamless and enjoyable profile management experience.
Execution (single execution) page to React (v24.36)This update brings the benefits of React’s component-based architecture to the interface, enhancing responsiveness and interactivity for users.
The navigation within app.elastic.io now displays page titles in the browser history for all React-powered pages. By incorporating descriptive titles for each page, users can easily track their browsing history and identify specific pages at a glance.
Retry Message button for the stopped flow (v24.36)This enhancement not only allows users to retry errors seamlessly but also provides a clear hint stating that the flow needs to be active for the retry function to work. By offering this convenient feature, users can easily manage and troubleshoot errors, promoting a more user-friendly and efficient workflow within the platform.
Enhance user visibility and control over flow operations by showcasing the live status of containers on the “Flow Queues” page. With this enhancement, users can now monitor the actual status of flows in real-time, empowering them with valuable insights into ongoing processes.
Since this trigger is initiated by another flow, displaying the CRON tab becomes irrelevant and can cause confusion. By removing this tab, users benefit from a more intuitive and streamlined interface, ensuring that flow configuration remains clear and concise.
Note: This feature requires to use Flow Linking component v1.1.1.
Recipes page (v24.36)This enhancement ensures that users receive more precise and informative explanations of errors directly on the UI, enabling them to quickly identify and address issues.
sailor-jvmTypeError: Invalid Version: when replacing the same component with a new one that uses a sailor version with ^.
component-pusher side as this service doesn’t have access to the package.json file.^.putOutToSea.catch and the error Invalid Version.1.0.0 (v24.36)Make Raw Request ActionUpsert Object ActionLookup Objects (plural) ActionLookup Object By ID ActionDelete Object By ID ActionGet New and Updated Objects Polling Trigger1.2.5 (v24.36)nodegit to 0.28.0-alpha.113.2.0 (v24.36)Get Item Availability Action1.6.1 (v24.36)Max Amount of Polling Pages text field for the Get New and Updated Objects Triggercomponent-commons-library version to 3.2.02.7.220.11.01.7.3 (v24.36)1.1.0 (v24.36)Get New and Updated Objects Polling Trigger1.4.0 (v24.36)Lookup Objects (plural) ActionDelete Object By ID ActionGet New and Updated Objects Polling Trigger2.5.9 (v24.36)4.0.31.1.1 (v24.36)flow-linking to component.json1.1.0 (v24.36)Webhook Triggercomponent-commons-library version to 3.2.02.7.22.8.4 (v24.36)The Replay ID validation failed when the Subscribe to PubSub trigger doesn’t emit messages for more than three dayscomponent-commons-library version to 3.2.02.7.22.5.0 (v24.36)Upsert Object Action