Modules§
- invalid_
client_ message - invalid_
computation - job_
invalid_ state - nats_
streaming_ unavailable - non_
nominal_ storage_ locator - permission_
denied - polling_
only_ computation - subscription_
auth_ expired - too_
many_ points - too_
many_ points_ for_ single_ series - unavailable_
result_ configuration - unsupported_
granularity - window_
negative - window_
too_ large - window_
with_ look_ back_ too_ large
Structs§
- Invalid
Client Message - Could not parse client message.
- Invalid
Computation - JobInvalid
State - The streaming compute job entered a terminal state unexpectedly. This can indicate a transient issue with the compute engine.
- Nats
Streaming Unavailable - The NATS-backed streaming transport became unavailable while running a streaming compute subscription. This can happen during a NATS pod rollout after the streaming compute restart budget is exhausted. Clients may retry by recreating the subscription. This uses INTERNAL because custom Conjure errors in this API do not support an UNAVAILABLE code; consumers should branch on this error name rather than HTTP status.
- NonNominal
Storage Locator - Permission
Denied - Polling
Only Computation - The requested compute contains nodes that support streaming but only via polling (not WebSocket). The frontend should use polling mode (HTTP requests) instead of WebSocket streaming for this query.
- Subscription
Auth Expired - The websocket subscription auth token expired. Clients should refresh credentials and re-establish the subscription.
- TooMany
Points - The subscription is operating on too many points.
- TooMany
Points ForSingle Series - The subscription is operating on a series that has too many points.
- Unavailable
Result Configuration - ResultConfiguration is incompatible with the requested compute.
- Unsupported
Granularity - Window
Negative - Window
TooLarge - Window
With Look Back TooLarge