Failed Charges Info (🧭 FUTURE)
✨ NEW TABLE - November 2025
🛠️ Partner API Alignment Migration
🧭 This table represents the post-migration state for
failed_charges_info.1️⃣ Migrate to this table by April 2026
2️⃣ Between April 2026 and July 2026, remove FUTURE__ prefix
Contains detailed information about failed charging sessions and their associated error data. Tracks technical failures, error codes, and charging session metrics.
SQL: FUTURE__failed_charges_info
Schema
| Column Name | Data Type | Description |
|---|---|---|
| Primary ID | ||
| id | INTEGER | Primary key (is charge_id) |
| Other IDs | ||
| charge_point_id | INTEGER | References the charge point where the failed charging session occurred |
| Timestamps | ||
| created_at | TIMESTAMP_NTZ | Timestamp when the failed charging session was initiated |
| completed_at | TIMESTAMP_NTZ | Timestamp when the failed charging session ended |
| Attributes | ||
| failed_reason | VARCHAR | High-level categorization of why the charging session failed |
| kwh | NUMBER | Amount of energy delivered before the charging session failed, measured in kilowatt-hours |
| firmware | VARCHAR | Version of firmware running on the charge point at time of failure |
| ocpp_reported_failure | VARCHAR | Raw failure message reported by the charge point via OCPP protocol |
| ocpp_end_reason | VARCHAR | Standardized OCPP reason code for why the charging session terminated |
| ocpp_end_reason_description | VARCHAR | Detailed description explaining the OCPP end reason code |
| ocpp_vendor_error_code | VARCHAR | Vendor-specific error code reported by the charge point |
| ocpp_reported_info | VARCHAR | Additional diagnostic information reported by the charge point via OCPP |
Changes from Last Version
Renamed columns:
charge_id→ 'id'cp_id→charge_point_id
** Removed column
external_id(was always null and unused)
Data inclusion criteria
- the
charge_point_idis among ids of the operator'sFUTURE__charge_points
Data flow
| Upstream tables | Downstream tables |
|---|---|
FUTURE__charge_points | none |
The failed_charges_info table
failed_charges_info table- To match
failed_charges_infoone needs to alignFUTURE__charge_pointswithcharge_points
Updated 15 days ago
