# Page Not Found

The URL `2025-release-notes/september-4-2025-trigger-event-filtering-in-yes-no-split` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [September 4, 2025 - Trigger Event Filtering in Yes/No Split](https://doc.batch.com/release-notes/release-notes/september-4-2025-trigger-event-filtering-in-yes-no-split.md)
- [September 24, 2025 - Attribute Change Trigger](https://doc.batch.com/release-notes/release-notes/september-24-2025-attribute-change-trigger.md)
- [December 18, 2025 - Long-term Trigger Management](https://doc.batch.com/release-notes/release-notes/december-18-2025-long-term-trigger-management.md)
- [September 29, 2025 - Push subscription native trigger event](https://doc.batch.com/release-notes/release-notes/september-29-2025-push-subscription-native-trigger-event.md)
- [December 19, 2025 - Limit email open tracking based on consent](https://doc.batch.com/release-notes/release-notes/december-19-2025-limit-email-open-tracking-based-on-consent.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://doc.batch.com/release-notes/release-notes/september-4-2025-trigger-event-filtering-in-yes-no-split.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://doc.batch.com/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://doc.batch.com/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/release-notes/release-notes/september-4-2025-trigger-event-filtering-in-yes-no-split.md`).

You may also use `Accept: text/markdown` header for content negotiation.