> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/salesforce/support/troubleshooting/manual-sync.md).
# Manual Sync
For Limio-initiated actions such as a new order on the Limio Shop or a cancellation performed in LFS, Limio will make sure to have Limio subscriptions in sync with Zuora subscriptions.
However, for non-Limio-initiated actions such as a Zuora-initiated renewal, a Zuora-initiated cancel, or a new order performed via a non-Limio Salesforce application, the Limio Subscription might be out of sync with Zuora.
To prevent this, Limio has introduced a sync feature which is now available in the LFS Manage Subscriptions tab (legacy) and flow.
When a user clicks the Sync button, LFS makes a call to Zuora to fetch the up-to-date customer subscription data into Limio. After Limio has been synchronised with Zuora, the list of subscriptions in LFS is updated automatically. Clicking on the Sync button in LFS triggers the synchronisation of all customer subscriptions at once.
If any of the subscriptions failed to sync, the notification will include the name of the subscription for further investigation.
---
# 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.limio.com/salesforce/support/troubleshooting/manual-sync.md?ask=&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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)