> 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/common-data-quality-issues-and-fixes.md).

# Common Data Quality Issues and Fixes

The issues we see most often, and how to resolve them.

### Missing tokens

**Symptoms:** Drivers can't charge. Low token count on the Partner Data tab.

**Common causes:**

* `date_from` parameter not supported correctly, so delta syncs miss new tokens.
* Initial full sync didn't complete.
* New tokens not picked up.

**Resolution:** Verify pagination and `date_from` filtering on the partner side. Request a manual full token reload from ENAPI support.

### Stale or missing locations

**Symptoms:** Chargers appear in partner apps that no longer exist. New installations don't appear.

**Common causes:**

* Removed EVSEs not marked with status `REMOVED`.
* Location failed validation.
* `last_updated` timestamps not updating when objects change.

**Resolution:** Mark removed chargers with EVSE status `REMOVED`. Verify `last_updated` is being written on every change.

### Tariff issues

**Symptoms:** Partners can't see prices, or displayed pricing doesn't match the actual tariff.

**Common causes:**

* Tariff IDs exceed the OCPI max length (36 characters).
* Tariffs not linked to connectors.

**Resolution:** Validate tariff ID lengths. Ensure every connector has an associated `tariff_id`.

### Sync count discrepancies

**Symptoms:** Expected count is consistently 1–2 higher than actual.

**Common causes:**

* Specific objects consistently fail validation and aren't stored.
* Partner's total count includes filtered objects ENAPI doesn't receive.

**Resolution:** Contact ENAPI support to identify failing objects. On the partner side, ensure total counts reflect only the objects actually returned.

### CDR validation issues

**Common issues:** Tariff cost inconsistency, missing required CDR fields, CDRs referencing sessions ENAPI doesn't have.

**Resolution:** Verify your CDR generation applies tariff dimensions consistently. Ensure all required OCPI CDR fields are populated. See [CDR Clearing](/cdr-clearing.md) for validation specifics.

### When to contact ENAPI support

Reach out for:

* Manual full sync or token reload requests.
* Persistent sync failures you can't identify.
* Specific failing objects you can't find on your side.
* Count reconciliation across many parties.
* Suspected translation engine issues.

Contact <help@enapi.com> or your dedicated Slack channel.


---

# 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/common-data-quality-issues-and-fixes.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.