> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/faq/c160/c163/q529.md).

# Why isn’t the app syncing across my devices or with the cloud and how do I resolve this issue?

If you are experiencing a sync issue, please make sure: 

* you are using the cloud version of the app and not the offline version.
* the app is open while uploading to the cloud (it won't upload in the background).
* your cloud account has [space for additional images](/manual/readme/account-management/check-image-limit.md).

If the syncing issue persists, please [contact us for support](/manual/faq/c169/q575.md).

## Related 

* [Article: How to check your cloud image limit in the web portal](/manual/readme/account-management/check-image-limit.md)
* [Article: How to check your cloud image limit in the mobile app](/manual/report-and-run-integrate/account-management/check-image-limit.md)
* [FAQ: Why am I unable to upload images to the cloud?](/manual/faq/c160/c163/q532.md)
* [FAQ: What are the differences between the cloud and offline versions of the app?](/manual/faq/c142/c143/q388.md)
* [FAQ: How do I fix issues with pending uploads, duplicates, or reports that aren’t saving or syncing between devices?](/manual/faq/c160/c163/q528.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reportandrun.com/manual/faq/c160/c163/q529.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.