Silent failure

The export succeeded, but the file is empty

Report the exported file size and require it to be greater than zero; a successful process is not proof of a usable artifact.

What it looks like

The export finishes on schedule and writes a file, but the observed file_bytes value is 0.

Why a heartbeat is green

The exporter completed without an exception, so a run-only monitor sees a healthy process.

Expectation that catches it

Add an output expectation that warns when file_bytes is less than 1.

Report it to Glnc

Measure the final artifact after the write completes, then send that byte count with the successful run receipt.

POST /api/v1/monitoring/checks/nightly-export/runs

{
  "result": "succeeded",
  "report_id": "nightly-export-20260830T020000Z",
  "evidence": {
    "file_bytes": 0
  }
}

Next step

Define one consequential expectation.

Read the API contract before reporting production evidence, or join the private beta to start with one recurring automation.

Glnc uses essential storage for the app. Optional analytics stay off unless you allow them.