Silent failure
The scraper got HTTP 200, but found nothing
Treat HTTP success and useful output as separate facts; report the item count and require it to be greater than zero.
What it looks like
The request receives HTTP 200 and the scraper exits normally, while items_found is 0.
Why a heartbeat is green
Transport success says the source answered; it does not prove the expected records were present or parsed.
Expectation that catches it
Add an output expectation that warns when items_found is less than 1.
Report it to Glnc
Send the parsed item count after validation so a changed page or empty payload cannot hide behind HTTP 200.
POST /api/v1/monitoring/checks/catalog-scraper/runs
{
"result": "succeeded",
"report_id": "catalog-scraper-20260830T041000Z",
"evidence": {
"http_status": 200,
"items_found": 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.