Sequence Order and Wildcards

Build ordered paths and capture intervening activity.

4 min readProduct documentationzinzu Usage FAQ

58. Must named events be adjacent without Any?

For a basic Sequence Order path A → B, the next processed record after A must satisfy B. An unexpected record can break that attempt.

Use A → Any → B when intervening records should be allowed and captured. Adjacency refers to the prepared input stream from the query’s sources and date range, not every record in every database.

Illustration: Named events without a wildcard.
Add Any when intervening records should be allowed and captured.

59. Can Any match zero intervening records?

Yes. In A → Any → B, B can immediately follow A. The wildcard hands the B record to B without consuming it as intervening activity.

No extra record is required merely because Any is on the canvas.

Illustration: Allow and capture records between A and B.

60. How do I capture activity between two actions?

Place Any between named events when you want to allow and capture activity between them.

Example: Login Failed → Any → Login Succeeded captures the intervening records while still requiring a later successful login.

Illustration: Capture activity between failed and successful login.

61. What activity can Any capture?

It captures eligible intervening records, including records that do not match a named Event.

Example: Product Viewed → Any → Payment Completed can capture a search, a coupon action, or a delivery-option change between the two required actions. All captured records count toward the sequence limit.

Illustration: Capture intervening checkout activity.

62. Does Any capture records from sources outside the query?

No. It sees the prepared stream from the query’s configured sources, within the selected range and eligibility rules.

It can capture records from those sources that do not match a named Event. It does not search unrelated tables automatically.

63. What if a wildcard record also matches the next named event?

The next named event takes priority. The wildcard hands the same record to that event.

For A → Any → B, a B record is matched as B, not first captured as another wildcard record.

Illustration: Allow and capture records between A and B.

64. How can I combine Any with Duration Length?

Use a named final action when that action defines the end of the period you want to measure.

Example: Product Viewed → Any → Payment Completed → Duration Length ≤ 1,800,000 ms → End finds matching activity spanning no more than 30 minutes.

The duration runs from the first matched record to the final matched record, including elapsed time across intervening activity.

Illustration: Checkout activity within thirty minutes.

65. Can a record that breaks one sequence start another?

Yes, for ordinary Sequence Order event mismatches the reducer can reset and retry the same record as a possible sequence start.

Example: A → A → B for query A → B can fail the first attempt, then use the second A to begin the successful attempt. Do not generalize this to every control failure or limit boundary; those follow their own reset rules.

Illustration: A mismatching record may start a replacement attempt.

66. Is the sequence limit separate for each wildcard?

No. It applies to the whole sequence, including named events, accepted repetitions, and wildcard-captured records.

Adding more wildcard positions does not create extra record allowances.

Continue readingAny-Order Matching
Search documentation · Esc to close
Open original image ↗