Install

Works with Drupal: ^11.3

Using Composer to manage Drupal site dependencies

Alternative installation files

Download tar.gz 10.52 MB
MD5: a80a6650e63c953f9cafd8a9c1419e05
SHA-1: 5b5d3be81eddd26641a8f1bfac8a07d1017e63c4
SHA-256: efa889f4eff213bf5074f4127cc8f840ab52b446260de9515b09f2bba0d225f8
Download zip 12.26 MB
MD5: 73257fe1c3b4c4bacc91fc46ceaf6f94
SHA-1: acffa1c2f9672685b5a11fca4ef411a14944b81d
SHA-256: cbd5f8990a3432d0db3507fac8ae379a4577c742e3dffdab14c42bca80fba5ea

Release notes

FlowDrop 2.7.1 is a bug-fix release for 2.7.0. A run now ends once, the way it was ended, and an
inbox resume no longer runs the same job as the queue worker. There are no database updates: clear caches after
updating.

Fixed

  • A cancel is not lost. A run cancelled from the session, the admin pages or the expiry reaper
    while it was executing could be finished as completed over the cancel and announced twice. It now stays
    cancelled, and a question a step raised as the run was cancelled is cancelled with it instead of staying answerable
    in the inbox (#3592486).
  • A finished run is not driven again by a late resume of a StateGraph or Playground run, or by a
    duplicate queue item.
  • An open question stays open across Pause and Resume, and a timer sweep no longer resumes a
    question somebody already answered.
  • Asynchronous runs no longer stall at the execution budget when FlowDrop Interrupt is enabled.
    Resolving the "Execution budget reached" item in the inbox no longer runs the same job as the queue worker: the run
    continues from the item the queue already holds.
  • An answer given while a run is busy is not lost. The run continues from the queue once the
    other process lets go of it, and an answer given while a resume starts is no longer missed.
  • An error after a run is saved does not rewrite it. A failing completion subscriber or snapshot
    is logged; the run keeps its outcome and results.

Before you upgrade

Read the "2.7.0 to 2.7.1" section of href="https://git.drupalcode.org/project/flowdrop/-/blob/2.7.1/UPGRADE.md">UPGRADE.md. In short: a queue worker
that finds a run held by another process now puts the item back instead of consuming it; the "Execution budget
reached" item leaves the inbox once the run continues; the execution queue has a new resume action, so
a site that processes the queue only on cron sees such a run continue on the next cron run; and exceptions thrown by
PipelineCompletedEvent subscribers are logged instead of escaping the engine. The full list is in href="https://git.drupalcode.org/project/flowdrop/-/blob/2.7.1/CHANGELOG.md">CHANGELOG.md.

Created by: d34dman
Created on: 18 Oct 2026 at 14:41 UTC
Last updated: 18 Oct 2026 at 14:45 UTC
Bug fixes

Other releases