v.26.4.15.0 (Hotfix)
This release includes the following bug fixes:
Bug Fixes
1. DataTable Timestamp
Fixed a time‑lag issue in DataTable’s Insert Row component when used inside a loop, the “Updated At” column recorded a timestamp ahead of the actual system time. Now the timestamp correctly reflects the exact system time at the moment of record insertion.
2. Server Busy Alert and Data‑Loss
Fixed an intermittent “Server busy” alert that appeared randomly during active sessions and caused unsaved changes to be lost, requiring rework. The platform now remains stable during development, and all user‑entered changes are properly saved without data loss.
Action Required
All agent’s slug names will be reset to the default slug after the agent is updated. Please ensure you take a backup of the flow before proceeding with the update and then rename the slug back to its original name afterward.
Limitations
1. Local Flow Creation Removed:You can no longer create local flows. All new flows including local flows will be now created directly within a designated project and tenant folder. [Refer here.]
2. Strict Naming Conventions:Flow names are currently case-sensitive, where it allows you to create separate flows with names that differ only by capitalization (e.g., testFlow and testflow are treated as two distinct flows).
Known Issues
1. The Loop component currently supports only linear execution. Connecting multiple downstream components from the loop output is not supported and may cause the flow to break. (Tentative fix: May 2026)
2. The Invoke Flow component currently fails when text input is passed from another component, throwing a “No variable found” exception. Passing external input into an invoked workflow is not fully supported in this version and may cause the flow to break. (Tentative fix: May 2026)
3.Deleting a project also removes all associated flows, and they cannot be recovered. (Tentative fix: May 2026)
3. If the description field is removed from the flow JSON before import, the workflow is still uploaded with an empty description. (Tentative fix: May 2026)
4. Flow names are user-specific, allowing multiple users to create flows with the same name, which may result in duplicate solution names and versions. (Tentative fix: May 2026)
5. Newly generated API keys currently apply to all workflow versions. This will be updated to restrict keys to specific versions in future releases. (Tentative fix: May 2026)
6. The Web Scraper component does not support extracting data from JavaScript-based web pages. (Tentative fix: May 2026)
7. The Shareable Playground feature is not functioning as expected. (Tentative fix: May 2026)
Released Date: 02.05.2026
