BOTLOBBIESWhat should I do if the bot stays on Starting?
First check whether access is active and whether the panel shows a specific account or connection warning. A Starting label means the connection checkpoint has not been confirmed; it does not identify the cause on its own.
Look for the instruction attached to the state
The panel may explain that credentials need recovery, access has ended, or the service cannot currently connect. Those messages are more useful than the Starting label alone. Confirm the selected bot and read the whole notice before generating another account-linking request. If the browser was restored from history or resumed after being offline, let the control view refresh so you are not acting on an old startup display. A stale page and a bot that never connected are different conditions even if their first screenshots look similar.
Avoid creating a restart loop
Do not press Restart repeatedly while a startup attempt is still being assessed. Each additional action can interrupt progress and make it unclear which attempt the next update describes. If the interface provides a supported restart for a persistently stuck connection with valid access, use it once and observe the resulting state. If it explicitly requests Epic recovery, follow that path instead. Restarting cannot replace a missing authorization approval, change an expired access period, or correct a bot identity selected by mistake.
Collect enough information for a useful report
Note when the attempt began, whether the state ever changed to online, and the exact visible warning. Check the public status page for a relevant current incident, while remembering that a healthy summary does not prove your individual session succeeded. Include whether Fortnite ever showed the bot in your party. Keep temporary codes, private login links, and account secrets out of the report. These checkpoints help support distinguish initialization, credentials, access, and a delayed browser update without guessing from a spinner alone.