> For the complete documentation index, see [llms.txt](https://sync.wiki.mksdtech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sync.wiki.mksdtech.com/collaboration/edit-conflicts.md).

# Edit conflicts

What happens when you change an object a teammate holds or has changed, and how to fix it.

Rhino Sync stops two people from changing the same object. When it can't give you an object, it undoes your change and tells you why.

<figure><img src="https://2088031227-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMFZITZJW4MHLYhDLac3k%2Fuploads%2Fgit-blob-b51ebc6c4b6883a648874aef8afe20b582864a07%2Fmock-objects-in-use.png?alt=media" alt="Your changes were undone dialog" width="444"><figcaption></figcaption></figure>

## Why a change is undone

Rhino Sync checks each change as soon as Rhino is idle. It undoes the whole change when any object in it is:

* **In use by a teammate.** Someone changed it and hasn't synchronized yet. The card shows their name and colour, with a hint such as `Released when Tomas synchronizes.`
* **Outdated.** A teammate changed and synchronized it after your last reload. The card is headed **Outdated**, with the hint `Reload to get their latest version.`

The dialog lists how many objects of each type were involved, such as `5 × Object` and `2 × Layer`.

## What to do

| Card              | Fix                                                                                                       |
| ----------------- | --------------------------------------------------------------------------------------------------------- |
| A teammate's name | Ask them in [Sync Chat](/collaboration/sync-chat.md) to synchronize, then click **Reload** and try again. |
| **Outdated**      | Click **Reload**, then try again.                                                                         |

## Find the objects

While the dialog is open, the objects are highlighted in red and can't be selected.

* Click **Zoom** to zoom to them.
* Click **Close** when you're done.

## Avoid conflicts

* Reload before you start work in an area.
* Synchronize when you finish a piece of work, so teammates can continue.
* Turn on a teammate's colour in **Users** to see what they hold. See [Users and colours](/collaboration/users-and-colours.md).

## Actions that never conflict

These don't reserve objects, so you can use them freely:

* Hiding, showing, locking and isolating objects, such as `Hide`, `Show`, `Lock`, `Unlock`, `Isolate` and `Unisolate`.
* Turning layers on or off, locking layers and expanding layers in the layer panel.