> For the complete documentation index, see [llms.txt](https://docs.coherence.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coherence.io/0.8/resources/troubleshooting.md).

# Troubleshooting

### Multi-scene setup

* When networked entities are added by loading a scene additively, mind that the `CoherenceMonoBridge` must be set to a *singleton mode*. In case of a non-singleton *monobridge* the Entity will search for a *monobridge* instance within its scene, and if none is found it will be created in that scene. This applies to both `CoherenceSync` and `LiveQuery` objects.

  For a complete control over `CoherenceMonoBridge` resolving you can use either `CoherenceSync.MonoBridgeResolve` instance event or `MonoBridgeStore.MonoBridgeResolve` global event. A `CoherenceMonoBridge` instance provided by the `MonoBridgeResolve` event takes precedence over the scene and singleton ones.

### Baking

* Sometimes packages cache gets staled and after updating coherence package you might face Unity still uses the old package version. Try to `Reimport all` or closing the project, deleting `Library` folder, and reopening the project again. It will clean and update packages cache, and use the version of coherence stated in `manifest.json`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coherence.io/0.8/resources/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.