Validation and delivery

ReportPlane separates synchronous acceptance from asynchronous destination delivery.

Before acceptance#

The runtime checks:

• request and envelope syntax;
• sender identity and enabled state;
• CIDR and identity-binding policy;
• allowed model scope;
• non-empty record data;
• required fields;
• field normalization and types;
• applicable ingest quotas.

A failure here returns an error to the sender and does not report the record as accepted.

After acceptance#

Accepted records enter a durable local spool. The dispatcher reads ready files, groups compatible records, builds destination rows, and writes batches through the warehouse adapter.

The system records usage and operational metrics around this flow.

Retry behavior#

Temporary dispatch errors follow the configured retry interval and attempt limit. A deterministic normalization/build error is tracked as a spool failure so it does not block valid files on every tick.

After the terminal condition, runtime policy decides what happens to the failed file. Operators should inspect logs and statistics rather than assuming an accepted request guarantees eventual storage under every permanent destination failure.

Schema changes during delivery#

Required-field validation is an acceptance concern. A record that was valid when accepted is not rejected at dispatch only because a field became required later.

Monitor the path#

Use:

• Live Monitor for recent runtime activity;
• ingest-client statistics for sender-specific behavior;
• model statistics for accepted data shape;
• destination statistics for warehouse delivery;
• Usage & Cost for quota and volume context.