> For the complete documentation index, see [llms.txt](https://btwb.gitbook.io/btwb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://btwb.gitbook.io/btwb/tempus/during-a-match/can-i-reconnect-to-a-match-ive-been-disconnected-from.md). # Can I reconnect to a match I’ve been disconnected from? Learn how to seamlessly reconnect to an ongoing Tempus match in the BTWB app after an unexpected disconnection, ensuring your workout data remains intact. ### 🔄 Reconnecting to an Ongoing Tempus Match Experiencing a disconnection during a Tempus match can be frustrating, but the BTWB app allows you to easily rejoin and continue your workout without losing progress. Here's how:​ 1. **Experiencing a Disconnection:** * While in an active Tempus match, if you happen to get disconnected (e.g., internet issues, app crash, or accidental closure), the match will continue without you. 2. **Accessing the Reconnect modal:** * If the app crashed, launch the BTWB app again. Upon reopening, a **Reconnect** modal will appear, prompting you to rejoin the ongoing match.​ * If you were kicked out to the home screen of the BTWB app, perform a pull-down refresh action to get the Reconnect modal to appear. 3. **Rejoining the Match:** * Tap the **Reconnect** button on the modal. You'll be directed back to your active match, exactly where you left off.​ 4. **Match Continuity:** * Each of the following timers, because the match continued without you, will accurately reflect the ongoing workout:​ * **Main Timer:** Displays the total elapsed time of the match. * **Round Split Timer:** Shows the duration of the current round. * **Movement Split Timer:** Indicates the time spent on the current movement. 5. **Continuing Your Workout:** * Proceed with your workout as usual. Tap on the active movement card to advance to the next movement, ensuring all progress is recorded seamlessly.​ * When you complete the match, log your result the same way you would had you never disconnected in the first place. *** ### 💡 Tips & Notes * **Automatic Progress Saving:** Tempus automatically saves your workout progress, allowing for smooth reconnections without data loss.​ * **Apple Watch Users:** The reconnection process is consistent across devices. If you're using Tempus on an Apple Watch, follow the same steps to rejoin an ongoing match.​ * **Preventing Disconnections:** To minimize unexpected disconnections, ensure your device has a stable internet connection and that the BTWB app is updated to the latest version.​ *** ### 🎥 Video Walkthrough {% embed url="" %} **Transcription:** If you happen to disconnect from a match, for whatever reason, Tempus makes it easy to reconnect to that match. Let's assume you're in the middle of your workout.​ Round 2 has started, and it's time to progress. So, tap on the active movement card. Pay attention that the main timer shows.​ Oh, it's 3 minutes and 2 seconds and counting up. Round 2 split timer shows 1 minute, 29 seconds and counting up.​ Movement split is 23 seconds and counting up. Kill the app to mimic the unexpected upgrades. Now, open the home screen.​ So, the reconnect modal is revealed. Tap the reconnect button to return to the match. You may notice that you're still on the second movement of round two.​ Main match timer has still been counting up. Round split timer has still been counting up. Movement split timer has still been counting up too.​ Let's progress to the next movement card. Verify that Tempus is still working as normal after reconnecting, despite you were away for a while.​ Note that the same flow applies to users in Tempus matches on their watch.​ --- # 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://btwb.gitbook.io/btwb/tempus/during-a-match/can-i-reconnect-to-a-match-ive-been-disconnected-from.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.