Timing and Branching
Compare elapsed durations and route outcomes through branches.
83. Does time spent on skipped activity count toward duration?
Yes. Duration is a difference between timestamps, not the sum of only the actions you selected.
A at 10:00 and B at 10:10 span 10 minutes even if many records between them were skipped. Skipped activity after the last accepted record does not extend the positive matched-set duration by itself.
84. Where does Duration Length start measuring?
Terminal Sequence Order Duration Length measures from the sequence’s first consumed record to its last consumed record. It does not start at the event immediately before the control.
Duration Length Branch compares an incoming record’s timestamp with the sequence start. Any-Order Duration Length spans the first and last accepted records, including accepted recurring records.
85. What happens exactly at the duration threshold?
A less-than-or-equal condition includes the boundary; a strict less-than condition does not. The same distinction applies to greater-than-or-equal versus strict greater-than.
Example: exactly 2,500 ms passes ≤ 2,500 ms but fails < 2,500 ms.
86. Can Duration Difference compare two copies of the same Event?
In Any-Order, yes. Select two different occurrences from the basket even if both use the same Event definition.
Each requires a separate physical record. The difference is the absolute timestamp gap, so it cannot be negative.
87. Do timing controls wait for a timer?
No. They evaluate source timestamps while processing input records. A condition becoming true in wall-clock time does not create a record or trigger a transition.
Terminal Duration Length evaluates at the end of the matched path, without needing another record after the final named event.
88. Does a timing control consume a record?
Sequence Order timing controls do not consume a separate physical record. A nonterminal timing control can evaluate the current record and hand that same record to the next event on the selected path.
Terminal Duration Length checks the already consumed sequence. Any-Order filters evaluate the accepted set rather than adding records.
89. Can a timing branch connect directly to End?
Yes. The branching control can select an End path without requiring another named event there.
All branch outputs still need connections. Branch evaluation uses an incoming record; reaching a timing control is not a promise that it will independently fire a timer.
90. Must GT, EQ, and LT all be connected?
Yes. The builder validates all three outputs of branching timing controls, even if only one outcome interests you.
Each path can continue through events or connect to End where permitted.
91. Can branch outputs have different thresholds?
The branching timing UI exposes one shared threshold. GT, EQ, and LT compare against that same value.
They represent outcomes around one threshold, not independently configured time limits.
92. Can Duration Length and Duration Difference be combined?
Any-Order: yes. Add one of each and combine the filters using AND or OR.
Sequence Order: a general timing control can be combined with one optional terminal Duration Length. Two general timing controls are not allowed, and timing nodes cannot connect directly to one another.
Funnel does not expose timing filters.