> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nekt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# TC Fleet as a data source

> Bring fuelings, tanks, vehicles, drivers, checklists and maintenance from TC Fleet to Nekt.

TC Fleet is a fleet and fuel management platform. It records fuelings at your own pumps and at gas stations, tank levels, vehicles, drivers, attendants, inspection checklists and maintenance orders. The Nekt connector reads that data through the TC Fleet open API and lands it in your Catalog, so you can analyze fuel consumption, costs and fleet upkeep together with the rest of your data.

## Before you start

You need two values from the TC Fleet panel, on the **Integração** screen:

* **Identificação da empresa** (company identifier)
* **Chave de integração** (integration key)

> [!WARNING]
>
> Each company has a single integration key. Clicking **Gerar nova chave** on the Integração screen replaces it immediately and the previous key stops working, which makes every extraction fail until the new key is saved in the source. Agree on the change with whoever manages the Nekt source before regenerating it.

## Configuring TC Fleet as a Source

In the [Sources](https://app.nekt.ai/sources) tab, click on the "Add source" button located on the top right of your screen. Then, select the TC Fleet option from the list of connectors.

Click **Next** and you'll be prompted to add your access.

### 1. Add account access

The following configurations are available:

* **Company identifier**: The **Identificação da empresa** field on the Integração screen of the TC Fleet panel.
* **Integration key**: The **Chave de integração** field on the same screen.
* **Start Date**: (Optional) The earliest data read on the first sync. Leave it empty to read the whole history.
* **Fuelings lookback (days)**: (Default: 7) TC Fleet does not report when a fueling was changed, so every sync reads again this many days before the last fueling already read. This picks up fuelings corrected in the panel after they were extracted. Increase it if your team corrects fuelings long after they happen.

Once you're done, click **Next**.

### 2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis.

> Tip: The stream can be found more easily by typing its name.

Select the streams and click **Next**.

### 3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.

* **Layer**: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
* **Folder**: a folder can be created inside the selected layer to group all tables being created from this new data source.
* **Table name**: we suggest a name, but feel free to customize it. You have the option to add a **prefix** to all tables at once and make this process faster!
* **Sync Type**: you can choose between INCREMENTAL and FULL\_TABLE.
  * Incremental: every time the extraction happens, we'll get only the new and changed data, which is good if, for example, you want to keep every record ever fetched.
  * Full table: every time the extraction happens, we'll get the current state of the data, which is good if, for example, you don't want to have deleted data in your catalog.

Once you are done configuring, click **Next**.

### 4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters.

To define your [Trigger](https://docs.nekt.com/runs/scheduling-and-triggers.md), consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times).

Optionally, you can define some additional settings:

* Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource [here](https://docs.nekt.com/get-started/core-concepts/resource-control).
* Determine when to execute an **Additional [Full Sync](https://docs.nekt.com/get-started/core-concepts/types-of-sync#additional-full-sync)**. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while. A weekly full sync is recommended: vehicles, drivers, tanks and other records deleted in TC Fleet are not reported by its API, so they only leave incremental tables on a full sync.

Once you are ready, click **Next** to finalize the setup.

### 5. Check your new source

You can view your new source on the [Sources](https://app.nekt.ai/sources) page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.

> [!WARNING]
>
> For you to be able to see it on your [Catalog](https://app.nekt.ai/catalog), you need at least one successful source run.

# Streams and Fields

## Available streams

The table below lists every stream, its **slug** (the exact identifier to pass when creating the source via API) and a short description.

| Stream | Slug | Description |
| - | - | - |
| Fuelings | `fuelings` | Every fueling: own pump, gas station, tank intake, transfers and checks, with volumes, values, readings and calculated consumption. Deleted fuelings are included, with `deleted_at` filled. |
| Tanks | `tanks` | Fuel tanks of each branch, with capacity, current volume and pumps. |
| Fuel Types | `fuel_types` | Fuels and additives (ARLA, oil) used in tanks, vehicles and fuelings. |
| Vehicles | `vehicles` | Vehicles and machines of the fleet, with the fuels they use and their expected consumption. |
| Drivers | `drivers` | Users with the driver profile. |
| Attendants | `attendants` | Users with the attendant (pump operator) profile. A user with both profiles appears in both tables. |
| Checklists | `checklists` | Checklists answered in the app (and pending ones), with every question and answer. |
| Maintenances | `maintenances` | Corrective and preventive maintenance orders, with parts, services, values, workshop and attachments. |
| Maintenance Categories | `maintenance_categories` | Categories that classify maintenance orders (engine, brakes, suspension). |

Column names are the TC Fleet API fields in snake\_case: `_id` becomes `id`, and references such as `_idEstablishment` become `establishment_id`. Nested objects and lists are stored as JSON text (marked **JSON string** below), for example `json_extract_scalar(vehicle, '$.info.plate')`. The most used values inside them also have their own columns, such as `vehicle_id`, `vehicle_plate` and `pump_volume_fuel` in **Fuelings**.

## Fields by stream

> [accordion] Fuelings
>
> **Slug:** `fuelings` · **Primary key:** `id` · **Replication key:** `timestamp_done`
>
> | Field | Type | Description |
> | - | - | - |
> | `id` | string | Unique identifier of the fueling |
> | `type_supply` | string | Fueling type: FVI internal (own pump), FVE external (gas station), FT tank intake, CW check, TRO/TRI transfer out/in, TO/TI tank out/in |
> | `status` | string | O normal; D divergence (the informed volume differs from the totalizer-calculated volume by more than 1 liter) |
> | `timestamp_start` | datetime | When the fueling started (UTC) |
> | `timestamp_done` | datetime | When the fueling finished (UTC), used as the incremental replication key |
> | `establishment_id` | string | Identifier of the branch where it was logged |
> | `establishment` | JSON string | Branch where it was logged (JSON object) |
> | `attendant_id` | string | Identifier of the attendant who logged the fueling |
> | `attendant` | JSON string | Attendant who logged the fueling (JSON object) |
> | `vehicle_id` | string | Identifier of the fueled vehicle |
> | `vehicle_plate` | string | Plate of the vehicle at the time of the fueling |
> | `vehicle_fleet_code` | string | Fleet code of the vehicle at the time of the fueling |
> | `vehicle_odometer` | number | Odometer reading informed in the fueling |
> | `vehicle_hourmeter` | number | Hour meter reading informed in the fueling |
> | `vehicle` | JSON string | Vehicle data: snapshot of the vehicle record at the time of the fueling, readings and photo URLs (JSON object) |
> | `driver_id` | string | Identifier of the driver |
> | `driver_name` | string | Name of the driver at the time of the fueling |
> | `driver` | JSON string | Driver snapshot at the time of the fueling (JSON object) |
> | `type_fuel_id` | string | Identifier of the fuel type |
> | `type_fuel_name` | string | Name of the fuel at the time of the fueling |
> | `type_fuel` | JSON string | Fuel type snapshot at the time of the fueling (JSON object) |
> | `tank_id` | string | Identifier of the tank the fuel came from (or that received it, for FT) |
> | `tank_volume_fuel` | number | Volume moved in or out of the tank, in liters |
> | `tank_invoice_value` | number | Invoice value of the tank movement |
> | `tank` | JSON string | Tank data for the fueling (JSON object) |
> | `pump_id` | string | Identifier of the pump (internal fuelings) |
> | `pump_volume_fuel` | number | Volume dispensed by the pump, in liters |
> | `pump_closing_final` | number | Pump totalizer reading at the end of the fueling |
> | `pump` | JSON string | Pump data for internal fuelings (JSON object) |
> | `pump_external_volume_fuel` | number | Volume fueled at the gas station, in liters |
> | `pump_external_invoice_value` | number | Invoice value at the gas station |
> | `pump_external_gas_station_name` | string | Gas station name |
> | `pump_external_gas_station_document` | string | Gas station CNPJ |
> | `pump_external` | JSON string | Gas station data for external fuelings, including latitude/longitude (JSON object) |
> | `calculations_km_realized` | number | Kilometers driven since the previous fueling |
> | `calculations_hour_realized` | number | Hours worked since the previous fueling |
> | `calculations_value_per_liter` | number | Price per liter |
> | `calculations` | JSON string | Values calculated by TC Fleet: realized distance/hours, expected and realized averages, variations and price per liter (JSON object) |
> | `cost_center_id` | string | Identifier of the vehicle's cost center at the time of the fueling |
> | `cost_center_name` | string | Name of the vehicle's cost center at the time of the fueling |
> | `cost_center` | JSON string | Cost center at the time of the fueling (JSON object) |
> | `type_integration` | string | Origin: api, korth, cta or vestro. Empty when logged in the app or the panel |
> | `id_integration` | string | Identifier of the fueling in its origin system |
> | `manually_created` | boolean | True when the fueling was created manually |
> | `manually_changed` | boolean | True after the fueling was edited in the panel or through the API |
> | `deleted_at` | datetime | When the fueling was deleted (UTC); null unless deleted |
> | `created_at` | datetime | When the record was created (UTC) |
> | `updated_at` | datetime | When the record was last changed (UTC) |

> [accordion] Tanks
>
> **Slug:** `tanks` · **Primary key:** `id` · **Replication key:** `updated_at`
>
> | Field | Type | Description |
> | - | - | - |
> | `id` | string | Unique identifier of the tank |
> | `name` | string | Tank name |
> | `situation` | string | Record status: A (active) or I (inactive) |
> | `establishment_id` | string | Identifier of the branch the tank belongs to |
> | `type_fuel_id` | string | Identifier of the fuel stored in the tank |
> | `type_fuel` | JSON string | Fuel stored in the tank (JSON object, see fuel\_types) |
> | `type` | string | Tank type: I (internal) or C (shared) |
> | `direction` | string | Tank orientation: horizontal or vertical |
> | `capacity` | number | Tank capacity, in liters |
> | `alert_level` | number | Alert level, in the same unit as the capacity |
> | `current_volume` | number | Current volume in liters, calculated by TC Fleet from fuelings |
> | `last_supply_date` | datetime | When the tank was last used in a fueling (UTC) |
> | `id_integration` | string | Identifier the company assigned to this record in its own systems (free text, not unique) |
> | `pumps` | JSON string | Active pumps of the tank, each with its current totalizer reading in lastClosingFinal (JSON array) |
> | `owner` | string | TC Fleet company identifier (slug) that owns the record |
> | `created_at` | datetime | When the record was created (UTC) |
> | `updated_at` | datetime | When the record was last changed (UTC), used as the incremental replication key |

> [accordion] Fuel Types
>
> **Slug:** `fuel_types` · **Primary key:** `id` · **Full table**
>
> | Field | Type | Description |
> | - | - | - |
> | `id` | string | Unique identifier of the fuel type |
> | `name` | string | Fuel or additive name, unique within the company |
> | `situation` | string | Record status: A (active) or I (inactive) |
> | `need_arla` | string | S when the fuel requires ARLA (DEF), N when it does not |
> | `is_additive` | string | S for an additive (ARLA, oil...), N for a fuel. Additives are left out of fleet consumption indicators |
> | `id_integration` | string | Identifier the company assigned to this record in its own systems (free text, not unique) |
> | `owner` | string | TC Fleet company identifier (slug) that owns the record |
> | `created_at` | datetime | When the record was created (UTC) |
> | `updated_at` | datetime | When the record was last changed (UTC) |

> [accordion] Vehicles
>
> **Slug:** `vehicles` · **Primary key:** `id` · **Replication key:** `updated_at`
>
> | Field | Type | Description |
> | - | - | - |
> | `id` | string | Unique identifier of the vehicle |
> | `plate` | string | License plate or identification, unique within the company |
> | `fleet_code` | string | Fleet code of the vehicle |
> | `document` | string | Vehicle registration document (CRLV / Renavam) |
> | `brand_code` | string | Brand code |
> | `brand_name` | string | Brand name |
> | `model_code` | string | Model code |
> | `model_name` | string | Model name |
> | `year_code` | string | Model year code |
> | `year_name` | string | Model year |
> | `situation` | string | Record status: A (active) or I (inactive) |
> | `establishment_id` | string | Identifier of the branch the vehicle belongs to |
> | `capacity` | number | Capacity of the vehicle's own tank, in liters |
> | `type_average` | string | How consumption is measured: ODOMETER (km/l), HOURMETER (l/h), ODOMETER\_HOURMETER (both) or KWH. Empty when the vehicle does not track consumption |
> | `type_fuels` | JSON string | Fuels the vehicle uses, each with its expected average (averageOdometer, averageHourmeter, averageKilowattHours) (JSON array) |
> | `type_vehicle_id` | string | Identifier of the vehicle type |
> | `type_vehicle_name` | string | Name of the vehicle type |
> | `type_vehicle` | JSON string | Vehicle type (JSON object) |
> | `cost_center_id` | string | Identifier of the vehicle's cost center |
> | `cost_center_name` | string | Name of the vehicle's cost center |
> | `cost_center` | JSON string | Cost center of the vehicle (JSON object) |
> | `axle_config` | JSON string | Axle configuration used for tire control (JSON object) |
> | `number_of_digits_hodometer` | integer | Number of digits of the odometer |
> | `number_of_decimal_hodometer` | integer | Decimal places of the odometer |
> | `number_of_digits_hourmeter` | integer | Number of digits of the hour meter |
> | `number_of_decimal_hourmeter` | integer | Decimal places of the hour meter |
> | `number_of_image_evidence` | integer | Number of photos required when logging a fueling |
> | `last_odometer` | number | Last odometer reading recorded in a fueling |
> | `last_hourmeter` | number | Last hour meter reading recorded in a fueling |
> | `last_supply_date` | datetime | When the vehicle was last fueled (UTC) |
> | `implement` | string | Attached implement |
> | `note` | string | Free-text note |
> | `value` | number | Value of the vehicle |
> | `id_integration` | string | Identifier the company assigned to this record in its own systems (free text, not unique) |
> | `owner` | string | TC Fleet company identifier (slug) that owns the record |
> | `created_at` | datetime | When the record was created (UTC) |
> | `updated_at` | datetime | When the record was last changed (UTC), used as the incremental replication key |

> [accordion] Drivers
>
> **Slug:** `drivers` · **Primary key:** `id` · **Replication key:** `updated_at`
>
> | Field | Type | Description |
> | - | - | - |
> | `id` | string | Unique identifier of the driver |
> | `user` | string | Login, unique and lowercase |
> | `name` | string | Full name |
> | `email` | string | Email address |
> | `document` | string | CPF (Brazilian individual taxpayer number) |
> | `driver_license` | string | Driver's license number (CNH) |
> | `company_register` | string | Employee registration number in the company |
> | `whatsapp` | string | WhatsApp phone number |
> | `situation` | string | Record status: A (active) or I (inactive) |
> | `force_change_password` | boolean | True when the user must change the password on next login |
> | `is_driver` | boolean | True when the user has the driver profile |
> | `is_attendant` | boolean | True when the user has the attendant profile |
> | `is_manager` | boolean | True when the user has the manager profile |
> | `is_super_user` | boolean | True when the user is a super user |
> | `establishment_id` | string | Identifier of the user's home branch |
> | `establishments` | JSON string | Branches the user can access, with notification settings (JSON array) |
> | `id_integration` | string | Identifier the company assigned to this record in its own systems (free text, not unique) |
> | `owner` | string | TC Fleet company identifier (slug) that owns the record |
> | `created_at` | datetime | When the record was created (UTC) |
> | `updated_at` | datetime | When the record was last changed (UTC), used as the incremental replication key |

> [accordion] Attendants
>
> **Slug:** `attendants` · **Primary key:** `id` · **Replication key:** `updated_at`
>
> | Field | Type | Description |
> | - | - | - |
> | `id` | string | Unique identifier of the attendant |
> | `user` | string | Login, unique and lowercase |
> | `name` | string | Full name |
> | `email` | string | Email address |
> | `document` | string | CPF (Brazilian individual taxpayer number) |
> | `driver_license` | string | Driver's license number (CNH) |
> | `company_register` | string | Employee registration number in the company |
> | `whatsapp` | string | WhatsApp phone number |
> | `situation` | string | Record status: A (active) or I (inactive) |
> | `force_change_password` | boolean | True when the user must change the password on next login |
> | `is_driver` | boolean | True when the user has the driver profile |
> | `is_attendant` | boolean | True when the user has the attendant profile |
> | `is_manager` | boolean | True when the user has the manager profile |
> | `is_super_user` | boolean | True when the user is a super user |
> | `establishment_id` | string | Identifier of the user's home branch |
> | `establishments` | JSON string | Branches the user can access, with notification settings (JSON array) |
> | `id_integration` | string | Identifier the company assigned to this record in its own systems (free text, not unique) |
> | `owner` | string | TC Fleet company identifier (slug) that owns the record |
> | `created_at` | datetime | When the record was created (UTC) |
> | `updated_at` | datetime | When the record was last changed (UTC), used as the incremental replication key |

> [accordion] Checklists
>
> **Slug:** `checklists` · **Primary key:** `id` · **Replication key:** `updated_at`
>
> | Field | Type | Description |
> | - | - | - |
> | `id` | string | Unique identifier of the checklist |
> | `name` | string | Name of the checklist template |
> | `config_checklist_id` | string | Identifier of the template that generated the checklist |
> | `establishment_id` | string | Identifier of the branch |
> | `date` | datetime | Day the checklist was generated for |
> | `status` | string | P pending, F finished. A pending checklist whose date has passed is late |
> | `finish_at` | datetime | When it was answered (UTC); null while pending |
> | `periodicity` | string | L free, D daily, S weekly, Q fortnightly, M monthly, A yearly |
> | `link_vehicle` | boolean | True when the checklist is tied to a vehicle |
> | `alert` | boolean | True when any checked option is flagged as an alert |
> | `justified` | boolean | True when the checklist was not done and a justification was given |
> | `justification_text` | string | Justification given in the panel |
> | `user_id` | string | Identifier of the user who answers the checklist |
> | `user_name` | string | Name of the user who answers the checklist |
> | `user` | JSON string | User who answers: id, name, login, document, company register, integration id (JSON object) |
> | `vehicle_id` | string | Identifier of the inspected vehicle |
> | `vehicle_plate` | string | Plate of the inspected vehicle |
> | `vehicle` | JSON string | Inspected vehicle: id, plate, fleet code, integration id (JSON object); null when not tied to a vehicle |
> | `questions` | JSON string | Questions in order, with type, requirements and answers. In option questions (CH, CO, S) value S marks the chosen option; in free text (L) and signature (SIG) the answer is the first value (JSON array) |
> | `description` | string | Checklist description |
> | `image` | string | URL of the photo taken in the checklist |
> | `image_vehicle` | string | URL of the vehicle photo taken in the checklist |
> | `latitude` | number | Latitude where it was answered |
> | `longitude` | number | Longitude where it was answered |
> | `address` | string | Address where it was answered |
> | `owner` | string | TC Fleet company identifier (slug) that owns the record |
> | `created_at` | datetime | When the record was created (UTC) |
> | `updated_at` | datetime | When the record was last changed (UTC), used as the incremental replication key |

> [accordion] Maintenances
>
> **Slug:** `maintenances` · **Primary key:** `id` · **Replication key:** `updated_at`
>
> | Field | Type | Description |
> | - | - | - |
> | `id` | string | Unique identifier of the maintenance |
> | `code` | integer | Sequential code of the maintenance within the company |
> | `name` | string | Maintenance title |
> | `description` | string | Maintenance description |
> | `date` | datetime | Maintenance date (the planned date while pending). A pending maintenance past this date is late |
> | `type` | string | C corrective, P preventive |
> | `status` | string | P pending, A in progress, F finished, C canceled |
> | `finish_at` | datetime | When it was finished (UTC); null otherwise |
> | `establishment_id` | string | Identifier of the branch |
> | `vehicle_id` | string | Identifier of the vehicle |
> | `vehicle_plate` | string | Plate of the vehicle |
> | `vehicle` | JSON string | Vehicle summary: id, plate, fleet code, integration id (JSON object) |
> | `category_maintenance_id` | string | Identifier of the maintenance category |
> | `category_maintenance_name` | string | Name of the maintenance category |
> | `category_maintenance` | JSON string | Maintenance category (JSON object) |
> | `supplier_id` | string | Identifier of the workshop (supplier) |
> | `supplier_name` | string | Name of the workshop (supplier) |
> | `supplier` | JSON string | Workshop: id, name, CNPJ (JSON object); null when none |
> | `cost_center_id` | string | Identifier of the cost center |
> | `cost_center_name` | string | Name of the cost center |
> | `cost_center` | JSON string | Cost center (JSON object); null when none |
> | `config_maintenance_id` | string | Identifier of the preventive plan that generated the maintenance; null for standalone ones |
> | `checklist_id` | string | Identifier of the checklist that generated the maintenance; null otherwise |
> | `itens` | JSON string | Parts and services: line, description, type (service or product), quantity, unit and total value (JSON array) |
> | `value_products` | number | Total value of parts, in BRL |
> | `value_services` | number | Total value of services, in BRL |
> | `value_total` | number | Total value of the maintenance, in BRL |
> | `attachments` | JSON string | Attachments: name, file URL and comments (JSON array) |
> | `id_integration` | string | Identifier the company assigned to this record in its own systems (free text, not unique) |
> | `created_at` | datetime | When the record was created (UTC) |
> | `updated_at` | datetime | When the record was last changed (UTC), used as the incremental replication key |

> [accordion] Maintenance Categories
>
> **Slug:** `maintenance_categories` · **Primary key:** `id` · **Full table**
>
> | Field | Type | Description |
> | - | - | - |
> | `id` | string | Unique identifier of the category (referenced by maintenances.category\_maintenance\_id) |
> | `name` | string | Category name |
> | `situation` | string | Record status: A (active) or I (inactive) |

## Implementation Notes

### Data Quality Considerations

* **Fuelings are snapshots**: the `vehicle`, `driver`, `type_fuel` and `tank` data on a fueling (and the `vehicle_plate`, `driver_name` and `type_fuel_name` columns) show the record as it was when the fueling happened. Use the `*_id` columns to join with the current records in **Vehicles**, **Drivers**, **Fuel Types** and **Tanks**.
* **Corrected fuelings**: TC Fleet only filters fuelings by the day they happened, not by when they were changed. Every incremental extraction reads again the days covered by **Fuelings lookback (days)** before the last fueling already read. A fueling corrected later than that window is only updated on a full sync.
* **Deleted fuelings**: fuelings deleted in TC Fleet are kept with `deleted_at` filled, on any date. Filter `deleted_at IS NULL` to analyze only valid fuelings.
* **Deleted records**: deleting a vehicle, driver, attendant, tank, fuel type or maintenance in TC Fleet is permanent and is not reported by its API. These records stay in incremental tables until the next full sync. Records with history are usually inactivated instead (`situation = 'I'`), which the connector does pick up.
* **Branches**: TC Fleet has no list of branches. Each record carries the branch identifier in `establishment_id`; ask TC Fleet for the branch names if you need them.
* **Status codes**: TC Fleet uses single-letter codes (for example `situation` `A`/`I` and maintenance `status` `P`/`A`/`F`/`C`). Their meaning is in the field descriptions above.
* **Checklist answers**: in `questions`, option questions (`CH`, `CO`, `S`) mark the chosen option with `value = "S"`; in free-text (`L`) and signature (`SIG`) questions, the answer is the `value` of the first item.

### API Limits & Performance

* TC Fleet allows 600 requests per minute per IP address. The connector stays well below that and reads 100 records per request. When TC Fleet asks it to slow down or is temporarily unavailable, it waits and retries automatically.
* Except for **Fuel Types** and **Maintenance Categories** (small lists, read completely on every run), incremental extractions read only the records created or changed since the last extraction. The last record of the previous extraction is read again on each run, which is expected.

## Troubleshooting

| Error or symptom | What it means | What to do |
| :- | :- | :- |
| "TC Fleet rejected the credentials" | The company identifier or the integration key is wrong, or the key was regenerated in TC Fleet (HTTP 401). | Copy both values again from the Integração screen of the TC Fleet panel and update the source configuration. |
| "TC Fleet is limiting the request rate" | Too many requests reached TC Fleet from the same IP address. | Nothing to do; the extraction pauses and resumes automatically. Avoid running several TC Fleet sources at the same time. |
| A fueling corrected in TC Fleet still shows the old values | It was corrected more than **Fuelings lookback (days)** after it happened. | Increase the lookback, or run a full sync of the source. |
| Deleted vehicles, drivers or tanks still appear | TC Fleet does not report permanent deletions. | Run a full sync, or schedule a weekly Additional Full Sync. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.