Reconciliation report for a rail
Answers “did we lose a message?” by evaluating E(m) = C(m) + T(m) + R(m) per rail over a declared window. What pages: a non-zero divergence, and a send with no captured return leg past the return-leg window. What does not: a hole in the vendor’s sequence, which is counted and listed here: the vendor numbers the whole cabin in one sequence, so a hole is usually another legacy system’s message. Whichever cycle is reported, it lists the rail’s open findings and its closed ones with their closure; closedCursor pages to older closures. The Courier deletes no cycle and no closure: they are audit evidence, and the client defines how long its database keeps them.
Parámetros de ruta
Parámetros de consulta
Respuesta
OK
Set on a channel's first cycle when the channel was registered more than a day before reconciliation first ran: nothing captured or sent before this instant was judged, and a divergence older than it is never reconciled automatically. Null when the cycle judged all it could.
Holes in the channel's own sequence over the cycle, or over the range when from/to are given; null when no sequence was measured: the rail has none, or no key that arrived could be read as one. Counted and exposed, never paged: the vendor numbers the whole cabin in one sequence, so a hole is usually another legacy system's message.

