Run health
Start/end, duration, error path, retry count, and the upstream response status.
RomeoApps-owned n8n reliability proof
Silent Success Lab
n8n can execute every node successfully while a token expires, a response shape changes, a filter matches nothing, or the final system receives no record. The missing layer is an outcome contract.
Synthetic fixtures only. No customer data, n8n credentials, production access, or live workflow writes are used here.
Synthetic run inspector
Select a case to see what a run-health check can observe, what an output contract can disprove, and where the workflow should pause before a client discovers the gap.
REVIEW · success unproven
The trigger and nodes completed, but the output count fell from a normal range of 8–30 to zero. That is a contract failure until the source response, auth state, and filter selectivity are checked.
observedboundaryknownmissingThe missing layer
A practical contract records enough state to distinguish “the workflow ran” from “the intended business event happened.”
Start/end, duration, error path, retry count, and the upstream response status.
Expected count window, freshness, required fields, schema hash, and duplicate key checks.
Downstream record ID, acknowledged write, or an explicit exception queue entry.
Alert, hold, or review when the result is suspicious—even when every node is green.
Fixed reliability diagnostic · USD 300
If a client workflow is failing quietly, I can inspect one public or approved-redacted seam and return a written state map, failure ledger, smallest repair sequence, and acceptance checks. Fit is confirmed in writing before payment; the first pass requests no credentials.
Request fit