For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
It’s possible that as you schedule a change to a flag, another member introduces a breaking change, or a conflict.
Conflicts occur for two reasons:
Another member updated the flag’s targeting that invalidates one or more of your scheduled changes
Another member scheduled a set of conflicting changes to be executed before your changes
LaunchDarkly warns members in the user interface (UI) when they save or schedule changes to the flag that introduce conflicts with other pending scheduled changes.
Here is an image of the “Confirm changes” dialog with a conflict:
A notification showing a conflicting scheduled change.
Despite this warning, a member could decide to save their conflicting changes anyway. If this happens, LaunchDarkly sends an email notification to the member whose changes now conflict. That member’s changes will not take effect at the time and date they were scheduled to.
Resolve conflicts in scheduled changes
If your scheduled changes conflict with other changes, you receive an email notification.
You can resolve the conflict and ensure your scheduled changes don’t fail in one of two ways:
Choose one of the two conflicting changes and delete the other. For example, you may have scheduled three targeting rules to be updated and someone deletes one of those rules, which causes a conflict. If this happens, you can update your scheduled changes to delete the scheduled changes to that rule. This ensures that the conflict is resolved and the remaining rules are updating successfully.
Update the conflicting changes so they no longer conflict. You can update your changes or the new scheduled changes to resolve the conflict and ensure both scheduled changes execute successfully.
