Update 1.7: Journeys — chains instead of single runs
Several automations can be joined into one route: when a segment finishes, the contact moves into the next.
Neu:
The chain actually runs:
When a segment completes, the contact is carried into the next one and started there. Every route used to end after the first segment — the transition edge in the diagram was a claim.
No loop possible:
Positions increase strictly, only live segments run, and if there is no contact the chain ends.
Build and rebuild:
A route is created together with its first segment in one go; further segments can be added, removed and reordered.
Failures stay visible:
The overview rolls failed runs and the segments' last run upward, so a problem cannot disappear inside one segment.
Existing work carried over:
Existing single automations were wrapped into one-segment routes — nobody had to rebuild anything.