The five verdicts
A failure takes priority over the other verdicts. With no failures, zero graded evidence takes priority over partial coverage, warnings and a clean pass. The app derives these labels from counts and evidence. The API returns summary fields and run status rather than a verdict word.
Conformance counters
data.summary contains:
For a conformance run:
warned overlaps graded checks, so adding it again double-counts them. Not tested and not applicable are separate counts; neither is a failure. Older reports can omit notApplicable.
Journey counters and authority
A charging journey counts exclusive outcomes:Run states
The final states are
completed, failed, cancelled and interrupted. An HTTP 200 from a report read can still contain an active state. Poll data.status with a deadline; use the suite CI recipe rather than accepting a successful HTTP response alone.
Why a warning is not a failure
OCPI requirement keywords distinguish required behaviour from recommendations. Declining aSHOULD is not a broken requirement, and a warning does not increment failed. A few warnings come from ChargerDojo’s own rules rather than a SHOULD, and the summary names them as ours.
Sources: OCPI 2.2.1 requirement keywords and RFC 2119 section 3.
ChargerDojo recommendations are not OCPI rules
A check can carry a ChargerDojo recommendation: advice from us where OCPI is silent, shown in blue with a bulb beside the status and explained when you open the check. It names its source and the date we read it. It is not a warning, never passes or fails a check, and changes no count and no verdict. The API returns it asrecommendations on each check, and the MCP checks tool labels it as ours.
Response time follows two separate rules:
- OCPI sets no response time. When one of ChargerDojo’s own limits stops a request (30 seconds of silence, or 60 seconds for the whole response), the check is Not tested, with the time it waited and the label
ChargerDojo limit. It is never failed and never retried, because OCPI tells a client not to queue and resend a failed request. A run that reaches its own 10-minute limit stops asinterrupted, keeps every check it already graded and sends no more. - We recommend answering within 10 seconds. Real counterparties give up sooner: Plugsurfing’s Roam OCPI FAQ documents a real-time authorization timeout configurable from 1 to 10 seconds. A slower answer is flagged on its check.