> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/license-entitlements/portal/offline-portal/syncing-usage-offline.md).

# Syncing Usage Offline

A sync reports usage from an offline computer without deactivating the license. It replaces the previous approach of deactivating the license to report consumptions.

A sync file can carry, for one license or every license in a bundle:

* **Consumptions** recorded on the license
* **Feature consumptions** recorded on consumption features
* **Device variables** set on the computer

The application keeps each consumption as a separate event until the server confirms it, and removes events only after you load the response file. Each event is applied once only, so uploading the same sync file twice never counts usage twice.

### Syncing Usage

{% stepper %}
{% step %}

#### Create the sync request

In the application, create a sync request file named `ls_sync.req`.
{% endstep %}

{% step %}

#### Upload the request

On a computer that is online, drop the file onto the upload area. You can also use the **click to select** link. The progress card shows how many products and usage events the file carries.

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2F82GFxgpNWh0cEWY1PVLv%2F05-sync-uploading.jpg?alt=media&amp;token=d3e9e147-3573-4d75-a606-e66c9e325299" alt=""><figcaption></figcaption></figure>

* Uploading a sync file
  {% endstep %}

{% step %}

#### Wait for processing

The server applies the usage events. Large sync files can take up to a minute. Keep the page open.

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FLaUATG1YOjQunAtuE2WS%2F06-sync-processing.jpg?alt=media&amp;token=793d3702-9d6f-4260-a30e-3b16c589ef57" alt=""><figcaption></figcaption></figure>

* The server applying usage events
  {% endstep %}

{% step %}

#### Download the response file

The download of `sync_response.lic` starts automatically. If it does not, click **Download sync\_response.lic**. The result page shows what was applied.

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FzL4PDixDItrolykz9Qgp%2F07-sync-complete.jpg?alt=media&amp;token=55b22d8c-2f7f-4d36-b44a-a74cac8ee8bf" alt=""><figcaption></figcaption></figure>

* Sync complete
  {% endstep %}

{% step %}

#### Load the response file

Copy `sync_response.lic` to the offline computer and load it in the application. The application removes applied events from its queue. It also updates the local license with current totals and entitlements.

{% hint style="warning" %}
Until `sync_response.lic` is loaded, every event in the sync stays pending on the offline computer. The application sends those events again with the next sync file. Load the response file even when the result shows rejected events.
{% endhint %}
{% endstep %}
{% endstepper %}

### Understanding Sync Results

The result page shows, per product, what the server applied, what it rejected, and what is still pending.

| Heading                        | Meaning                                                                       |
| ------------------------------ | ----------------------------------------------------------------------------- |
| **Sync complete**              | Every event and device variable in the file was applied                       |
| **Sync completed with issues** | Some events or device variables were rejected, or some products got no result |
| **Nothing was synced**         | The server had nothing to apply from this file                                |

The four totals under the next steps count events across all products: **Events applied**, **Events rejected**, **Still pending**, and **Device variables saved**.

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FQe6SczCeip3HHO6bEGKT%2F08-sync-completed-with-issues.jpg?alt=media&amp;token=9c28dcdd-a8cf-4199-a768-6c19c0fbbe13" alt=""><figcaption></figcaption></figure>

#### Product Cards

Each product has its own card, marked **Synced**, **Needs attention**, or **Not synced yet**.

| Row              | Shows                                                                                      |
| ---------------- | ------------------------------------------------------------------------------------------ |
| License usage    | Consumptions added (for example "+12 from 12 events") and the license total after the sync |
| Feature `<code>` | Consumptions added to that consumption feature                                             |
| Offline checkout | Units left in this computer's offline reservation from a consumption pool                  |
| Device variables | Variables saved, and any that were not saved with the reason                               |

A product marked **Not synced yet** got no result from the server. Its events stay on the computer and go out with the next sync file.

#### Rejected Events

Rejected events are grouped by reason. Expand a group to see the error code and the event IDs. Each group indicates what the application does next:

* **Kept on the computer and sent again with the next sync** — the event can succeed later, for example once the license has consumptions remaining.
* **Removed by the application, it will not be sent again** — the event can never be applied.

Rejected events expanded with codes and event IDs

| Error code                                     | Reason                                                                         | Next sync  |
| ---------------------------------------------- | ------------------------------------------------------------------------------ | ---------- |
| `license_not_enough_consumptions`              | Not enough consumptions left on the license                                    | Sent again |
| `feature_not_enough_consumptions`              | Not enough consumptions left on the feature                                    | Sent again |
| `pool_quota_exhausted`                         | The consumption pool, or this computer's offline checkout, has nothing left    | Sent again |
| `invalid_sync_event`                           | The event data is invalid, or the same event ID was sent with different counts | Removed    |
| `negative_consumptions_not_allowed`            | The license or its pool does not allow negative consumptions                   | Removed    |
| `unsupported_product_feature`                  | The feature is unknown, expired, or not a consumption feature                  | Removed    |
| `license_not_consumption`                      | The license is not a consumption license                                       | Removed    |
| `invalid_pool_type`, `missing_company_feature` | The pool configuration or the account plan does not allow it                   | Removed    |

#### Device Variables

A device variable that was not saved shows one of two reasons: device variables are not included in the plan, or the device variable limit has been reached.


---

# 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.licensespring.com/license-entitlements/portal/offline-portal/syncing-usage-offline.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.
