BOTLOBBIESWhat does a configuration conflict mean when saving bot settings?
A configuration conflict means the version you edited is no longer the current saved version. Another request, tab, or device may have changed it, so the service asks you to reconcile the current values rather than overwrite newer settings blindly.
Understand why the save was refused
The configuration endpoint expects a valid revision and can return a conflict together with the current bot information. This protects changes that happened after your page loaded. It is different from a catalog item being unavailable or the bot failing to connect to Fortnite. If you see this notice, first inspect the current selected bot and saved fields. Repeatedly sending the unchanged old form does not make its original revision current again and may keep producing the same refusal without resolving the discrepancy.
Choose which changes you still want
Compare your intended edits with the latest values shown by the panel. Keep the current configuration where it is already correct and reapply only the differences you still need through the normal controls. If another tab or device is editing the same bot, stop those competing changes while you reconcile. This is particularly useful when one screen changes an outfit and another changes an emote: the final saved record should represent an intentional combination rather than whichever stale form happened to submit last.
Distinguish repeated conflicts from live application delays
Once the save succeeds, a delayed game appearance is a separate application question. Do not keep treating it as a revision problem if the new configuration is already recorded. If conflicts continue with one editing session and a freshly loaded record, note the affected fields, sequence, and exact notice for support. Leave private configuration secrets out of the report. The useful evidence is that a fresh edit conflicts unexpectedly, not a full account dump or a guess that the bot's Epic authorization must be replaced.