Understand the Results and Limits

Matched sets show the order in which records actually matched, even though the query did not require that order. Different orders can therefore produce different displayed patterns.

3 min readProduct documentationzinzu Any-Order Behavior User Guide

Status	Meaning*
COMPLETED	The required occurrences and qualifying filters passed. An absence check, if configured, also passed within its observation window.
INCOMPLETE	The candidate did not complete, or the negated event occurred after the required set qualified.
CONTROL_FAILED	A candidate failed a system filter and the engine advanced to a new candidate window.
LIMIT_REACHED	The candidate reached the sequence record limit without completing.
COMPLETED_LIMIT_REACHED	A qualified absence check closed successfully at the sequence record limit.
IGNORED	An input record was not accepted into the matched set. This is a record status, not a completed sequence.

Intermediate accepted records can be marked INCOMPLETE while a set is being collected. Judge the outcome from the completed or final result for that sequence, not from an early record alone.

Ignored records do not fill required occurrences. However, while a sequence is active, they count toward its record limit, including during a negation observation window.

Application verification. Illustrative Results modal: two COMPLETED patterns with different actual matched orders. Counts and durations are example values; matched timestamps are illustrated below. — Illustrative Results modal: two COMPLETED patterns with different actual matched orders. Counts and durations are example values; matched timestamps are illustrated below.

One completed set in its actual matched order. Documentation illustration based on the supplied guide and native UI components. Not a live query execution. — Illustration: One completed set in its actual matched order.

Configuration Limits

Up to 10 event occurrences in the basket, including copies and any negated event.
At least one required event.
One filter of each type, for up to three system filters.
One global AND/OR operator for the system filters.
One negated event, which cannot be a system filter’s target.
Recurring maximum count from 1 to 50.
The sequence record limit applies independently of the recurring maximum.
Any-Order does not use graph connections, wildcards, Start/End nodes, or branch controls.

Avoid Overlapping Event Definitions

One record may match multiple event definitions. zinzu assigns it to the first unsatisfied matching occurrence in the saved basket order. Each physical record fills only one required occurrence. Assignments are not reconsidered later. With overlapping filters, basket order can therefore affect which sets complete. Use distinct conditions when you need unambiguous attribution. Identical event copies are allowed, and each copy requires a separate record.