v0.32.2
July 4, 2026
Consolidation release: anti-duplicate reliability, consistent access control, and clearer WIP.
-
Improvement
No more duplicate items or events
On flaky networks or double submits (n8n/webhook retries, double clicks), creating items and raising events no longer produces duplicates. `POST /items` and `POST /events/raise` accept an **Idempotency-Key**: same key = same operation, exactly once. Flows with "entityRef required" now truly deduplicate per entity.
-
Improvement
Flow import without duplicates
Importing the same flow twice (or creating one with an already-used code) is now blocked with a clear message, instead of silently creating a duplicate flow family.
-
Improvement
WIP: "warning-only" is now visible
When a phase in *warning-only* mode goes over its limit, admitted items now show an **"Over WIP limit"** badge — the saturation used to be invisible. In the Kanban board, items queued for capacity are separated from the ones actually in progress.
-
Security
Consistent role-based visibility
A user now sees (and can open) only the flows, items, their history/activity and Process Maps they can actually operate on — the rule introduced in v0.29 now applies to every view, not just the flow list.
-
Security
Safer MCP keys and WIP fail-closed
MCP keys are no longer accepted in the query string on the main transport (only on the legacy one that requires it) and are redacted from logs; MCP flow publishing applies the same integrity checks as REST. Inconsistent WIP setups (redirect to a missing state, unresolvable limit expression) now park the item safely instead of silently ignoring the limit.
-
Integration
Webhook tasks follow the connector
A webhook task can now **follow** its n8n connector's body template — after a resync, changes propagate automatically instead of staying on an old snapshot. The designer also warns about duplicate state names and makes them distinguishable in dropdowns.
-
Improvement
Chrome extension: clearer environment switch
When switching the FlowSharp environment, tenants connected to a different environment are highlighted with a badge and an explicit confirmation — no more silent divergence between the shown and the operational environment.