> For the complete documentation index, see [llms.txt](https://doc.iscope.online/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.iscope.online/documentation/11.-troubleshooting-and-faq.md). # 11. Troubleshooting & FAQ * **No rallies joining?** Check Auto-rally is On (card switch), your monster filter isn't excluding them (skipped rallies are logged), and the leader whitelist is right. If the log shows only heartbeats for a long time, Stop → Start the worker. * **"Account is in use on another device" / auto-stop?** The game session was taken by another login (phone, PC). Close the game there, then press Start — or let the auto re-login reclaim it if an email is on file. * **Bubble shows "No active bubble" but you applied one?** The countdown refreshes from the server at each login/reconnect. If the worker was stopped when the shield ended, the card shows the truth; apply a new shield. * **Stamina packs not being used?** Auto stamina must be On *and* the account running. The bot only loads when stamina is below 150 (about 1,000 per refill), only uses packs already in the account's inventory (10/25/50/100), and skips anything that would pass 9,999 stamina. * **Gather not starting?** Remember the exclusivity rule — having Auto-rally or Rally setter on turns gather off. Also check troop counts and that no marches are stuck (stale marches are pruned automatically). * **Login fails?** Re-fill the credentials (email resolve or manual) — the game rotates session credentials between logins, and old values stop working. * **Account shows "stopped" after a while?** See the session note in *Stay Online & Family bubble sharing*; the bot never runs alongside an active phone session. --- # 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, and the optional `goal` query parameter: ``` GET https://doc.iscope.online/documentation/11.-troubleshooting-and-faq.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.