BOTLOBBIESWhy does the panel say saved when the change is not visible in Fortnite?
Saved means the website recorded the configuration; live application is a separate step. A bot that is reconnecting, absent from your party, or waiting for a command can therefore have a saved choice that is not yet visible in Fortnite.
Read the whole result message
The configuration endpoint can distinguish a successful save from a problem applying that saved configuration to the connected bot. Do not read only the word saved and assume every later step completed. Look for a pending, retry, or connection explanation accompanying it. The stored selection is useful because you should not need to rebuild it merely to investigate a delayed live result. Record the state you actually received before changing the same slot again and replacing the evidence of the original attempt.
Check the account you are watching
Compare the selected bot in the panel with the member visible in your current Fortnite party. A correctly saved outfit for another owned bot will not change the account beside your player. Also check whether the intended bot has connected and joined this lobby. A browser selection and a game party can diverge after you switch records or rebuild the group. Correct that mismatch before treating a missing cosmetic as a catalog error or a reason to relink an otherwise healthy Epic account.
Recover without competing updates
Wait for the pending operation or follow the displayed retry action, then inspect the same bot again. If another tab changed the configuration, resolve the revision conflict rather than overwriting it blindly. Repeatedly choosing many items can create a sequence where each visible update belongs to a different request. For support, note the original item, the distinction between saved and applied, and whether the connection was active. That focused report is more actionable than a general statement that every control failed.