> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/release-notes/release-notes/november-12-2025-wait-for-event.md).

# November 12, 2025 - Wait for Event

We are introducing a new timing and split feature in Trigger Automations, the "Wait for Event" step. This step allows to **wait for up to 4 events over a defined time period.**\
It works as follows: once the user enters the Event step, they are put on hold for a customer-defined duration. Two outcomes are possible:

* The user triggers one of the expected events. They will then immediately proceed down that event's branch (without waiting for the timer to expire).
* The user does not trigger any of the expected events. They will wait for the timer to expire and then proceed down the timer's branch.

This feature **unlocks news use cases** as:

* Creating channel fallbacks using retargeting events in the event step (e.g., wait 1 hour for a Push Open, if not, send an SMS).
* Managing transactional flows (e.g., wait for email validation in an onboarding scenario before processing to the next step).

[Check our documentation](/getting-started/features/customer-engagement-platform/orchestration/trigger-automations.md#adding-steps-to-the-scenario)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.batch.com/release-notes/release-notes/november-12-2025-wait-for-event.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.