FlowDrop 2.6 Stable Adds AI-Assisted Workflow Editing and Runtime Improvements

Maintainers released FlowDrop 2.6.0 on 22 September 2026 as the first stable release of the project's 2.x line. The release adds AI-assisted editing that can modify workflows directly in the Drupal editor. According to the release notes, the assistant can add nodes, connect steps and change settings instead of only explaining how to make those edits. Actions that change a workflow still require confirmation, and editors can undo them like other changes.

The assistant can also continue through several operations from a single request instead of stopping after its first action. FlowDrop 2.6.0 requires Drupal 11.3 or later within the Drupal 11 release line. Site settings separately control the AI Assistant and Command Console, with the Command Console disabled by default and the AI Assistant enabled by default. Turning both off removes their button from the canvas.

Runtime changes focus partly on workflows that pause and later resume. Earlier runs could become progressively slower because FlowDrop reread their full execution history each time they resumed; version 2.6 reads only the history it needs. The release also adds missing database indexes across run tables and removes indexes that were not useful, targeting faster cleanup operations and run-listing screens.

Several fixes address execution behaviour. A paused run could previously fail with a maximum-iterations error despite having work remaining, while blocking a user account did not actually stop that account's runs. Version 2.6 corrects both behaviours and also cleans up unanswered questions left behind by completed runs. Workflows containing an unrecognised connection type are now rejected when saved rather than failing later during execution.

Administrators also get more visibility into stored execution data through Drupal's status report and the drush flowdrop:retention:report command. The report shows how much run history is stored and how old it is, but it does not delete that history, and version 2.6 does not provide an automatic retention-deletion setting. The previous one-megabyte limit on a single stored value is now configurable, allowing sites working with larger documents or conversations to raise it when necessary.

Upgrading requires drush updatedb followed by a cache clear. The update adds a database column and an index and fills them for existing runs in batches, so sites with substantial run history may take longer to complete the process. Installations moving from FlowDrop 1.x must first upgrade through version 1.6.0, which the release notes identify as a security release.

Developer-facing changes include stable error_code values on API refusals. Integrations that currently match the wording of an error message should move to those codes because the message text is no longer part of the API contract. Custom implementations of FlowDropPipelineRuntimeInterface are also expected to implement FlowDropPipelineJobLookupInterface; implementations that do not will continue through a slower fallback and raise a deprecation notice. The release notes say those methods are scheduled to move onto the runtime interface in FlowDrop 3.0.0.