v.26.9.30.1 (Hotfix)

This release includes the following bug fixes:

Bug Fixes

Scheduler

Fixed an issue where the execution status of some scheduled Flows was not updated correctly in Manager. A retry mechanism now identifies execution records with unsynced status updates and ensures the accurate status is reflected in Manager.

Known Issues

1. Scheduled Flow Execution: When a flow is scheduled with an interval of more than one hour, it may execute one additional time. (Tentative fix: Oct 2026) 
2. The embedding functionality in the Robility LLM component is currently not working.( Tentative fix: Oct 2026) 
3. Deleting a project also removes all associated flows, and they cannot be recovered.(Tentative fix: Oct 2026) 
4. If the description field is removed from the flow JSON before import, the workflow is still uploaded with an empty description. (Tentative fix: Oct2026)
5. 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: Oct 2026)
6. Newly generated API keys currently apply to all workflow versions; this will be updated to restrict keys to specific versions in a future release.(Tentative fix: Oct 2026)
7. The Web Scraper component does not support extracting data from JavaScript-based web pages. (Tentative fix: Oct 2026)

Existing Limitations

1. A user cannot edit or schedule a flow that has already been scheduled by another user within the same project.
2. The Model Provider integration is currently accessible only to the user who configured it. Other users within the same project or agent cannot access or use the configured integration.
Workaround: Use the LLM component by passing the required LLM connection as an input. This enables other users to utilize the LLM functionality without requiring direct access to the configured Model Provider integration.
3. The Pulse Componentdoes not support variable mapping for the Security Keyand Public Key input fields when dynamically loading prompts.
Workaround: The component works as expected when the values are provided directly instead of using variable mapping.
4. Version History will track only workflows published after the upgrade. Previously published versions remained available in Robility Manager but will not appear in Version History or be eligible for scheduling. To enable these features, export and rename the workflow (for example, FlowName.1.0.0 → FlowName), then republish it.
5. The Loop component has been enhanced to resolve stale and duplicate Datatable updates. Updating the component will remove all nodes within the Loop component and associated Datatable values. Back up the workflow before upgrading.
6. When processing large files with the Read File component, increase the Timeout and Retry Count settings to ensure successful OCR extraction.
7. The invoke flow in tool mode does not work with the configured slug name.
Workaround: After connecting the tool node, manually update the slug name before using it.

Release Date: 30.09.2026