> For the complete documentation index, see [llms.txt](https://docs.wiclax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wiclax.com/en/all-competition-types/multisport-raid.md).

# Multisport raid

This type of competition consists of a series of timed 'heats' - whatever name we give them, with interruptions between each heat. The total race time is the sum of the heat times.

## Settings

The competition is managed in a single stage, to the extent that the different heats take place simultaneously.

The setting consists of defining intermediate split points for each start and end of heat.

The general start can be used as the start of the first heat. The general finish will ideally be the end of the last heat, in order to upgrade participants to finisher status.

These splits allow you to create a segment for each heat. And the crucial detail lies here: every segment will be set with the option `Timed segment (not the others)`. This is what will make the final race time calculated as the sum of the timed sections.

<figure><img src="https://1159484786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJRt17XpwpUQzKYPTGL7Z%2Fuploads%2FQQ0wLSnGyLojkQtJAoK0%2Fimage.png?alt=media&amp;token=0f56ee08-3014-4528-b09f-d1444b8fb5a4" alt="" width="530"><figcaption></figcaption></figure>


---

# 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://docs.wiclax.com/en/all-competition-types/multisport-raid.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.
