26.3.18.2

1. Backward Compatibility: Robility Flow now supports backward compatibility. When prompted for a component update, users can choose to update or skip it. Both existing and new workflows will continue to function without any deprecation issues.
2. Local Flows: A notification is now displayed stating: “Local flows will be deprecated soon. Please migrate your local flows to Manager Flows.”  This serves as a proactive reminder to ensure continued support in future releases.
3. Message History: A Message History option has been introduced in the flow menu, allowing users to view messages stored using the message history component.
Note: This feature is currently under development and is not functional yet.

Bug Fixes

1. Datatable Automation – Insert Row:
a. Resolved an issue where executing the Insert Row component in tool mode resulted in a 500 Internal Server Error. This was caused by invalid JSON values, which are now properly handled.
b. Fixed an issue where passing input values to the Insert Row component caused an exception: “JSON object of type Message is not JSON serializable.” The component now handles inputs correctly without errors.

Limitations

1. When a user has multiple project folders in the Robility flow, creating a new flow using “Load from Local” in Robility Manager does not display flows from other folders, even if they belong to the same project and tenant.
2. The flow name must be unique and cannot be duplicated, even across different tenants. Currently, it allows us to create flows with names that differ in case sensitive (e.g.,testFlow and testflow)

Known Issue

1. Deleting a project will also delete all flows associated with that project.
2. If the description field is manually removed from the flow JSON before import, the workflow still uploads successfully with an empty description.
3. Since flow names are user-specific, different users can create flows with the same name. This can lead to duplicate solution names and versions being published simultaneously.
4. The Upsert Row component where passing input values to the component causes an exception: “JSON object of type Message is not JSON serializable.” This will be fixed in the upcoming version.
5. The Web Scraper component does not support extracting content from JavaScript-based web pages.

Release Date: 18/03/2026