| Aspect | Non-streaming | Streaming (IngestData) |
|---|---|---|
| Error scope | Error indicates that specific call failed | Error may mean none of the data points in that request were saved |
| Client action | Handle the error appropriately | Retry all data from that request |
| Data overwrite | Not applicable | Sift overwrites existing data on retry |
| Retransmission risk | Low; discrete calls are self-contained | Higher; client is continuously streaming so it is not guaranteed that an error is related to the last request sent |
Streaming
Streaming error reference
The behavior of errors differs between non-streaming and streaming API calls.
Recommendation: Break data into discrete batches instead of streaming continuously. If a failure occurs, only the latest batch needs to be retried, which improves reliability and reduces the impact of errors on overall data flow.