Silent failure

The sync succeeded, but it wrote zero rows

Report the number of records written and require at least one when the sync is expected to move data.

What it looks like

The sync reports success while records_written is 0 for a run that should copy new data.

Why a heartbeat is green

Connecting, querying, and exiting cleanly can all succeed even when the result set is empty.

Expectation that catches it

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

Report it to Glnc

Count committed destination records, not rows merely read, and include that count in the completion receipt.

POST /api/v1/monitoring/checks/warehouse-sync/runs

{
  "result": "succeeded",
  "report_id": "warehouse-sync-20260830T031500Z",
  "evidence": {
    "records_written": 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.