Destinations
Connect a data model to storage and understand provisioning, delivery status, and failure handling.
A destination is the delivery configuration between one or more selected data models and a warehouse backend. It includes the backend type, target settings, credential reference, and operational state.
Create a destination
Destinations are normally created through New Warehouse by selecting models. The management API also exposes destination creation and retrieval.
/management/v1/warehouses/management/v1/warehouses?project_id={projectId}/management/v1/warehouses/{id}Delivery lifecycle
Accepted records enter a local durable spool. The dispatcher groups ready records and writes them through the destination adapter. Temporary failures can be retried according to runtime policy.
A deterministic row-normalization or batch-build failure is treated as a spool failure rather than being attempted on every dispatch tick forever. When retry is enabled, it follows the configured interval and maximum attempts. When retry is disabled, the terminal action is applied immediately.
One malformed ready file does not block valid files from being batched and delivered.
Status and statistics
Use the destination detail page to inspect its configuration and statistics. A healthy ingest response with missing warehouse data points to destination or dispatch state; an immediate HTTP validation error occurs earlier in the path.
Schema provisioning
When supported and enabled, ReportPlane creates missing storage structures and adds compatible fields. It does not erase existing data to force a model change.