BOTLOBBIESWhy is the bot Ready but my Fortnite match has not started?
The bot's Ready state is only one checkpoint. Your real player and party still need an accepted activity and the appropriate game-side readiness, and the game can reject or delay matchmaking after the bot has prepared successfully.
Read your player's state in Fortnite
Look at the account you are actively playing, not only at the bot's animation or panel label. Confirm that your player is in the intended party and that the agreed real player leads it. Check the selected experience and any message shown to the player. The browser can report a supported bot action without performing every game-side choice for you. If your own character is not ready or the activity requires attention, repeating the bot's Ready command does not address that missing player action.
Check whether the party changed after readiness
A friend joining, a leadership transfer, or a rebuilt group can change the conditions under which the bot was previously prepared. The readiness logic checks the current party and can reject a result when membership or leadership changes during the operation. Compare the actual lineup and leader again instead of assuming that a green state from several moments ago applies unchanged. Keep one person responsible for the next setup decision so simultaneous invitations and activity changes do not create another uncertain transition.
Distinguish waiting from a rejection
If the game has started searching, observe whether it is still waiting or has returned an explicit cancellation or restriction. A search delay and an error message require different descriptions. Note the wording, time, activity, and whether the bot remains connected. The service does not guarantee immediate matchmaking or a particular match composition. Preserve that distinction when asking for help: a prepared bot, an accepted party, and a completed game search are separate outcomes, and the missing one tells support where to investigate next.