v0.79.6
August 7, 2026
Honest responses, sequences that never stall. Second stabilization wave: concurrent saves have a single winner, activity sequences always resume — even after a crash —, scheduled items start when you actually move them, event rules now work on human phases too, and the n8n contract says the same thing everywhere: UI, snippets and guides. No migrations: a simple upgrade.
-
Improvement
Sequences always resume, from every channel
Completing an activity — from the UI, the API, a callback or a timeout — now always arms the next activity in the sequence, with a durable claim: a mid-flight crash is recovered automatically within half an hour, and a replay never produces double dispatches. Automatic pauses and async activity timeouts also survive a restart at the wrong moment.
-
Improvement
Concurrent saves with a single winner
When two people save the same item's data starting from the same version, exactly one now goes through: the other gets a clear conflict and reloads fresh data. A version check sent with the wrong type is rejected with an explicit error instead of silently switching itself off.
-
Improvement
Scheduled items: they start when you move them
Moving an item waiting for its scheduled start now actually starts it: real start date, original schedule preserved, no double start from the scheduler. And if creating an item hits an entry problem, the response is an honest success with the id and automatic recovery — no more errors inviting you to recreate (and duplicate) the item.
-
Feature
Event rules now work on human phases
A phase assigned to an operator can now react to external events: when the expected event arrives, only that channel's rules fire, the transition overrides the wait and the activities of the left phase are closed with a full audit trail. Previously those rules, though configurable in the designer, were never evaluated.
-
Security
Historical outcomes redacted in rules too
Historical outcomes of child-flow launch activities are now shown redacted in the automatic-rules context and in the activity update response as well: the identity of whoever started the parent flow no longer travels through any read channel. The child's data remains readable through the supported binding.
-
Integration
A consistent n8n contract everywhere
Callback authentication, generated snippets and the guides (Italian and English) now say the same thing: correct header, identifiers all taken from the same Webhook node frame, complete test payload. And the event idempotency key now asks for a stable source identifier, with an explicit warning about leaving the placeholder in place.