An httpjson pagination typo: request finished does not establish a complete interval
Distinguish a normal final page from a template execution failure.
The gap after a successful first page
Distinguish a normal final page from a template execution failure. Do not approve a complete interval merely because the first page was published. Include the termination reason in the Truthound completion table; valid first-page rows cannot establish that there was no next page. [1, 2, 3]
The failure shown by the automated report
Beats #53288 is a Bug Hunter report showing a pagination execution error treated as successful completion despite fail_on_template_error=true. The supplied test publishes only the first page and receives no interval error. This automated report is not our independent reproduction or a measurement of customer data loss. [1]
Two termination controls
Use a two-page synthetic endpoint, introduce a nextLink typo and compare termination reason, verified pages and required keys. Hold partially published intervals. Keep a normal final-page omission as a separate control, retaining error signals and reconciling missing and unexpected source keys independently. [1, 3]
Completion after an error following A
The illustrative endpoint requires pages A and B. After a template execution error following A, approved completion is 0. Observed 0 meets the error-state condition; 1 fails because B was not read. The policy does not force completion 0 on an actual normal final page. [1, 3]
Check prepared termination meaning
Truthound Core Python SDK 3.3.2 can compare prepared allowed_complete_flag and interval_complete_flag using ColumnPairValidator with relationship="==". The operator interprets the termination contract and observed error signal into non-missing flags. The SDK does not repair httpjson error propagation or pagination. [1, 2, 3]
Reconcile both status and keys
Correct the template, reconcile the failed interval by stable keys and test error propagation on the target version. A normal final page without nextLink differs from a runtime template typo. Passing the state check does not replace the data-key reconciliation. [1, 3]
Application conditions
Capture the actual pagination termination contract and template-error signal, and reconcile data keys separately.
Alternatives
Correct the template, rereconcile the interval by stable keys and test the target error-propagation behavior.
Limitations
The SDK does not repair error propagation; the public automated test is not our installed-environment reproduction.
Evidence
- Event checked
- Subject checked
- Modified
