A configuration apply hit a conflict
What to do when a configuration change stops partway or conflicts with a newer version, so you keep the changes that already worked.
Read the current resource first
A configuration change reports a conflict, expires, or stops partway through. Keep the existing plan or resource reference, then inspect the current state through the authorized surface you used.
Do not apply the entire change again just because the client lost its response. Some resources may already have changed.
Separate the outcomes
Nothing was applied and the plan expired: inspect the current configuration and prepare a new review through a supported operation. Do not extend the old approval yourself.
Another change altered the resource: compare the current version and values with the intended change. Replan only the remaining difference. Do not overwrite another administrator's update blindly.
Some changes are verified: preserve them. Identify each unresolved resource separately; do not assume that everything rolled back.
An apply response was lost: read back the affected resource before retrying. A client error is not proof that the write failed.
The operation is unavailable: stop and use the currently supported account control or contact Lithi. A management operation name in a reference is not a usable control by itself.
Keep the same permission boundary
Use the proper administrative identity for the selected account. A work key does not gain membership, policy, source, destination, or finance authority from a configuration file.
Do not remove a restriction or broaden a credential to clear a conflict. A changed destination, budget, or approval policy needs review in its own right. A repaired configuration also does not approve paid work.
Confirm each result
Success is a current read-back of every intended resource, with any unapplied part explicitly accounted for. Stop if a write, external effect, or resource owner remains uncertain.
Use Contact Lithi with the safe plan or resource reference, affected operation, error code, current version when available, and observation time. Send a redacted description of the difference, not secret configuration, credentials, or full customer payloads.