FlowDrop 2.7 Adds In-Editor Workflow Testing and Execution Fixes

Following its September release of version 2.6, maintainers of the FlowDrop Drupal module published three stable 2.7 updates on 17 and 18 October 2026. According to the project's release notes, version 2.7.0 brings workflow testing into the editor, while 2.7.1 addresses execution failures and 2.7.2 corrects a configuration interface problem.

The changes affect Drupal teams building and operating automated workflows, particularly those involving background queues, cancellations and human approval steps. The execution fixes address cases in which a cancelled run could subsequently be recorded as completed, or competing resume operations could interfere with a workflow awaiting input. Existing installations also face configuration and database update requirements.

FlowDrop 2.7.0 introduces a Test mode directly within the visual workflow editor. Previously, users accessed the Playground through a separate page to test workflow behaviour. The new Edit/Test switch makes the Playground available alongside the canvas, allowing operators to move between workflow construction and testing without leaving the editor.

The 2.7.0 release notes also describe a Runs list for inspecting workflow executions and a diagnostic capability called Doctor. The diagnostic system can examine an unsaved workflow draft, identify problems and apply available corrections as a single undoable edit. The standalone Playground page is deprecated as testing moves into the editor.

Workflow chat configuration changes in the same release. FlowDrop previously attempted to identify the node responsible for receiving chat messages based on node names. Version 2.7 instead uses explicit configuration in the workflow's Playground settings, and newly created workflows do not automatically receive chat functionality. The upgrade process is designed to preserve chat configuration for existing workflows.

More consequential runtime corrections arrived with FlowDrop 2.7.1 on 18 October. According to the release notes, cancelling a running workflow could previously leave its final status vulnerable to a later completion event. A workflow cancelled through a session, administrative action or expiry process could subsequently be marked completed, with duplicate completion notifications also possible. The patch changes the execution handling to preserve cancellation and cancel unanswered questions associated with the affected run.

The release also addresses attempts to resume workflows that have already completed. Late resume requests and duplicate queue items could cause an execution to be driven again after reaching a terminal state. The corrections cover StateGraph and Playground execution paths, where competing operations could otherwise attempt to continue the same run.

Human-in-the-loop workflows receive several related fixes. These workflows pause execution when an operator must answer a question, approve an action or provide information before processing continues. The release addresses cases in which an unanswered question was not preserved correctly across pause and resume operations, and in which a timer could attempt to resume a question that had already been answered.

Asynchronous execution is another focus of the patch. With FlowDrop Interrupt enabled, a workflow reaching its execution budget could remain stalled, while an answer submitted through the interrupt inbox could compete with a queue worker attempting to continue the same job. The revised handling is intended to prevent competing resume paths and retain answers submitted while execution is already in progress. Failures in completion subscribers or snapshot operations are also logged without changing an execution outcome that has already been saved.

These corrections concern workflow execution and state management rather than a formally designated security update. Their operational relevance is strongest for installations that depend on background processing or operator intervention, where a cancelled or interrupted workflow must retain a consistent execution state. The reported fixes are documented by the maintainers and have not been independently reproduced by The DropTimes.

Upgrading from FlowDrop 2.6.0 or an earlier 2.7 alpha requires database updates using drush updatedb, followed by a cache rebuild. The 2.7.0 release notes recommend a maintenance window for installations with substantial execution history because an update adds an index to the pipeline table. Version 2.7.1 does not introduce additional database updates but still requires caches to be cleared.

Queue configuration may also affect how quickly paused workflows resume. Version 2.7.1 introduces a resume action for the execution queue, meaning installations that process queues only through cron may continue resumed workflows at the next cron run rather than immediately. Operators should review this behaviour when checking their existing execution arrangements.

Custom integrations require a separate compatibility review. Seven pipeline control and snapshot API routes have moved under /api/flowdrop/, while the older paths remain available as deprecated aliases in the 2.x series. The associated Drupal.org change record remains marked Draft, although the stable release explicitly references the API changes. Developers using hard-coded endpoints should review those integrations before upgrading, particularly because the deprecated aliases are scheduled for removal in version 3.0.

The subsequent 2.7.2 patch, also released on 18 October, fixes a configuration editor regression that caused expanded groups to collapse while users were typing. The latest stable release supports Drupal 11.3 and later within the Drupal 11 release line. Installation through Composer uses composer require 'drupal/flowdrop:^2.7', with the applicable upgrade instructions and workflow checks remaining important for existing sites.