3. Find Repeated Actions with Recurring
Recurring allows the event immediately before it to repeat up to a specified number of additional times. Use it when an action may happen repeatedly before the next required event.
Unlike a wildcard, Recurring allows repetitions of that specific event, rather than any activity.
Build the Query
Drag Recurring from System Defined Events onto the canvas. Place it after the event that can repeat, then set Maximum recurrences.
Start → Added to Cart → Recurring (3) → Payment Completed → EndThis query finds an Added to Cart event, followed by up to three additional Added to Cart events, and then Payment Completed—all for the same EventOwner.
Sample Scenario
A customer adds several items to their cart before paying. You want to capture this behavior without creating a separate query for every possible number of additions.
With Maximum recurrences = 3, all these sequences can match:
- Added to Cart → Payment Completed
- Added to Cart → Added to Cart → Payment Completed
- Added to Cart → Added to Cart → Added to Cart → Payment Completed
- Added to Cart → Added to Cart → Added to Cart → Added to Cart → Payment Completed
The setting allows up to four occurrences in total: the initial event plus three repeats. It does not require exactly three repetitions.
When to Use It
- Shopping activity: Repeated cart additions before payment.
- Login attempts: Repeated failed logins before a successful login.
- Service retries: Repeated failed requests before a successful response.
Other actions are not automatically allowed between repetitions. Add a wildcard separately where your pattern needs to allow other activity.
Next: Submit the query and view results.
Note: Currently, zinzu supports only one Recurring control per query. This limit may change in future releases.