> For the complete documentation index, see [llms.txt](https://docs.enapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enapi.com/data-quality/monitoring-your-connections.md).

# Monitoring Your Connections

When and how to check the Data Quality page, depending on what's happening with your connections.

### After completing a new handshake

Check the page after the first sync cycle (within 24 hours). If counts stay at 0, go to the handshake page and check for errors.

### After a new roaming agreement activates

**Remember:** new and updated data flows automatically after activation, but the full current state requires an initial sync ([How ENAPI Syncs OCPI Data](/technical-documentation/how-enapi-syncs-ocpi-data.md)).

Once the initial sync has run, open the **Partner Data** tab and find the new partner:

* **If you're a CPO:** verify tokens from the eMSP are arriving.
* **If you're an eMSP:** verify locations and tariffs from the CPO are arriving.

### Ongoing monitoring

Check weekly — especially if you see an unexpected increase in failing sessions, auth, or commands. Look for:

* Sudden count drops on a module that had steady counts.
* Zero counts on a module you'd expect to have data.
* Consistent gaps between expected and actual counts.
* Stale data — last sync timestamp several days old.

### Verifying ENAPI against your own system

The most reliable sanity check is comparing Data Quality counts against the equivalent in your own platform. The rule of thumb: **compare against your full object set, not your active one.**

<table><thead><tr><th width="184.75390625">If you're checking…</th><th>Your reference should be</th></tr></thead><tbody><tr><td>Locations</td><td>All locations, all statuses — including <code>REMOVED</code></td></tr><tr><td>Tariffs</td><td>All tariffs, including those not currently linked to connectors</td></tr><tr><td>Tokens</td><td>All tokens your system has ever issued, including expired and revoked</td></tr></tbody></table>

If those match (or are close), your sync is healthy. If there's a gap, either ENAPI is missing objects or your system is filtering more aggressively than ENAPI stores.

This check is useful any time — after a new handshake, after a migration from another hub, after a major system change on your side, or just as a periodic audit.


---

# 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.enapi.com/data-quality/monitoring-your-connections.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.