Available history depends on stored readings and the asset–hardware associations included by the endpoint.
How far back can history be queried?
The inspected Command history endpoint does not establish a guaranteed retention period or maximum lookback. It selects active asset–hardware associations and clips queries to asset creation and association start.
An empty result is not proof that no reading ever existed. Check permissions, asset assignment, measurement selection and the supported retention period.
Request and rate limits
The inspected controller does not establish production request quotas, maximum asset count, maximum date span or response size. Absence of a limit in this controller does not mean unlimited service capacity.
Use bounded date ranges, positive aggregation intervals and one aggregation for each sensor type. Avoid increasing query size indefinitely after a timeout.
Production quotas and retry guidance must be confirmed before publishing numeric limits.
Late readings and reconciliation
Re-query overlapping historical periods to reconcile readings that arrive later. Store historical results separately from the latest-state display.
Timestamp guards exist in persistence, but they do not establish strict event ordering for the delivered live stream. Compare timestamps before replacing a latest-state value.
No maximum lateness or guaranteed reconciliation window has been established by this review.
Corrected readings
The history response contains timestamp/value points without an explicit correction flag, revision number or ingestion timestamp. Consumers cannot reliably identify a correction from response metadata alone.
Do not assume a changed point is a newly inserted reading, that every correction generates a live event, or that older history is immutable.
Missing readings
Preserve null values as missing data. Do not substitute zero. Aggregated results cannot establish that every original device reading was received.
Required confirmations before publication
| Topic | Required answer |
|---|---|
| Retention | Guaranteed queryable period and any plan or device differences. |
| Request limits | Maximum date span, assets, interval constraints and response size. |
| Rate limits | Quota, burst/concurrency limits and retry guidance. |
| Date boundaries | Inclusive/exclusive start and end semantics and bucket alignment. |
| Late readings | Expected arrival delay and supported reconciliation window. |
| Corrections | Replacement/versioning rules, notification behaviour and audit availability. |
| Raw recovery | Whether a supported Command API supplies individual missed readings. |
This article remains a draft until the service owner confirms these details.