Any-Order Matching
Collect required actions without enforcing their order.
67. When does an Any-Order sequence start?
It starts when a record is accepted for a required positive event occurrence. Records unrelated to all positive requirements do not start it.
A control can reject a candidate or cause a replacement window, so a matching event name alone does not guarantee a retained sequence start.
68. What happens when an already-satisfied event repeats without Recurring?
The additional record is normally ignored unless another required copy remains unsatisfied.
For A + B, A → A → B normally uses the first A and B. The second A does not replace the first timestamp. While the candidate is active, the ignored record still counts toward its record limit.
69. Can unrelated records cause Any-Order to reach its limit?
Yes. Once a sequence is active, subsequent processed records count, including skipped records.
With limit 5 and requirements A + B, records A → X → X → X → X stop the candidate before a later B. X does not fill a requirement but still consumes observation capacity.
70. Does changing basket order affect Any-Order results?
Basket order does not require events to occur chronologically in that order. Distinct, non-overlapping requirements can match in any order.
Identical copies each need a separate record. When a timing filter refers to particular copies, check which matched records serve as its endpoints. Use distinct definitions where possible to make the intended requirements clear.
71. Does Any-Order find every possible matching combination?
No. It uses a streaming candidate and resets after completion or applicable failure. It does not enumerate every subset or overlapping assignment.
For A + B, A → B → B does not reuse the first A to produce two completed sets.
72. What if the last requirement matches exactly at the record limit?
Normal completion takes precedence.
With limit 3 and requirements A + B, A → X → B completes on record 3 if its controls pass. If negation is configured and the set qualifies at that boundary, it closes as COMPLETED_LIMIT_REACHED rather than continuing observation.
73. Can a sequence have only one required event?
Yes. The Any-Order builder requires at least one positive event. Without filters or negation, a matching record can complete the single-event set.
A Duration Difference filter needs two different selected occurrences. A single-event set has zero total span at its first match.
74. Does Any-Order wait when a minimum time difference is unmet?
It can retain the older endpoint, discard a too-early candidate for the other endpoint, and consider a later matching record.
Example: A + B with a gap of at least 10 seconds. A at 0 and B at 3 do not qualify; B at 12 can satisfy the gap. The system evaluates incoming data records, not a real-time timer. Other filters can change the combined decision.