> For the complete documentation index, see [llms.txt](https://eventx-hq.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eventx-hq.gitbook.io/knowledge-base/event-setting/readme/testing-event-flow.md).

# Testing Event flow

#### When you are not yet familiar with the features and functions available on EventX 2.0 platform, before creating your actual event we highly suggest the following:

1. Create a Testing event

* You will be able to test and explore the available features with your testing event without affecting your actual event set up\
  ![](/files/8N8sXcwa1MZJ98RY88nv)

2. Be mindful of your Testing quota.\
   Here's a friendly reminder about your quota.
3. Your total Attendee Pax is given ***extra 5%*** count to cater to your testing needs and avoid consuming your actual paid quota.\
   (e.g. Total subscribed Pax: 1000 +5% (50)= 1050)
4. You may delete an attendee. To know more please read on [Attendee removal feature](https://eventx-hq.gitbook.io/knowledge-base/attendee-management/attendee-roles-and-status/attendee-removal-feature)
5. Once an attendee quota has been used, deleting an attendee does not restore the quota.
6. Once a testing attendee has been added/ registered in the event. We will not be able to clear the testing data for your event.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://eventx-hq.gitbook.io/knowledge-base/event-setting/readme/testing-event-flow.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.

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.