CR.M023

Completion report of an M023 request, published in JSON after the R6X and C6X flows it asked for. It tells the requester that the publication is finished: no further data is expected once the report has been issued.

The report carries one entry per requested PRM, so it feeds one data point per PRM, each in its own source.

How the file is recognised

CR.M023 files are recognised from their name only. The flux code in that name is also what the key is built from, which is why a report for another flow than R63 does not produce an M023_R63_CR key.

Anatomy of the R63 and CR.M023 file names

A .zip is accepted in place of the .json.

Warning

A renamed file is skipped: no data point, no error. Keep the name Enedis published.

Insights configuration

Property Value
Meter number of the source idPrm of each entry of prmDemandes
Mapping config of the variable See below

See Source configuration for the other properties.

Mapping config

M023_{code flux}_CR
Segment Description Values
{code flux} Flux code read from the file name, second segment R63 for a report answering an R63 request

Example

M023_R63_CR

Data point
Timestamp The 14 digit timestamp of the file name, read as Europe/Paris and stored in UTC
Value 1 when publication is PUBLIE
0 in every other case, NON_PUBLIE included
Tip

A value of 0 says the publication did not happen for that PRM. The reason is in the recevabilite and motif fields of the report, which are not stored — keep the file to investigate.

What is not stored

  • The synthese counters and the fichiersPublies list.
  • The recevabilite and motif of each PRM.
DOCS 2026.08 Documentation changelog →