New "Refund" Usage Breakdown for Exceptional Credit Adjustments
We’re introducing a new refund usage breakdown to transparently adjust credit consumption in rare cases affected by platform-side technical issues.
To ensure fairness, we’ve added a new refund
value to the usage breakdown types. This is used only in exceptional situations where technical issues on our side may have caused unintended or excessive credit consumption.
In these cases, if precise job-level recalculation isn't feasible due to affected data, we apply a credit refund at a more general level—per day and credit type (kbc_ppu
, sql_ppu
, cdc_ppu
). These refunds appear as negative values in the kbc_usage_metrics_values
table with "usage_breakdown": "Refund"
.
Key points:
- When is this used?
Only when platform-side issues affect credit consumption and prevent exact recalculation. - What does it mean?
A fair adjustment to your credit usage, applied transparently and based on the best available information. - Where will it appear?
- In the
kbc_usage_metrics_values
table with"usage_breakdown": "Refund"
. - In project and organization dashboards (e.g., Credit Usage Breakdown).
- Automatically included in KPI metrics on your dashboards for consumed credits.
- In the
No action is required on your part. This ensures your reported credit consumption reflects actual usage, even when exceptional issues occur.