> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/experience-editor/tutorials/intermediate-fire-extinguisher-training/limitations-and-alternative-approach.md).
# Limitations and alternative approach
When you add a recording through a triggered effect, it's synchronized with the main timeline. For example, if you use the Skip to Time IFX to skip forwards 10 seconds on the main timeline, the recording will also skip forward 10 seconds. If you use a Skip to Time IFX to go back to a point on the main timeline before the point when the recording was triggered, the recording will disappear.
For the fire extinguisher experience described in the previous sections, we used a Skip to Time IFX to create a loop. If a user selects an option a few seconds before the end of the loop, they may not see the full recorded response. There is a reduced risk in this case because each response is short.
To ensure that all recordings play in full, you can use an arrangement like that shown in the following image. You move recordings to the main timeline. You then use Skip to Time IFX, both as triggered effects and on the main timeline, to jump to appropriate points based on user activity. This alternative approach is demonstrated in the [Intermediate: Undersea educational content](/engage/experience-editor/tutorials/intermediate-undersea-educational-content.md).
Alternative timeline arrangement (select to expand)
---
# 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.engagevr.io/engage/experience-editor/tutorials/intermediate-fire-extinguisher-training/limitations-and-alternative-approach.md?ask=&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.
