Subscription Stream

🚧

Stream and Data

If the stream has new data to send, it will be sent immediately. However, if new data keeps coming up constantly, the stream will send the most updated result of each query in five-second bursts.

If the stream does not have new data to send, then it will send the most updated result of each query in one-minute bursts.

When the query reveals an execution error, a message will be sent through the SSE stream with this schema:

event:error
data: {"error_message" => "Something went wrong with the entry.","metadata":{"probe_id":"2"}, "query_id":"query_id_value", "entry_id":"entry_id_value"}
  • The stream won't be killed.
  • The other subscription's queries will continue sending the messages.
  • The entry that reveals an error will stay in an error state until the update entry point is used.

Subscription Limits

  • The maximum queries per subscription is 16.
  • The number of subscriptions is capped by the number of licenses, with a minimum of 500.
  • A subscription is deleted after two minutes, the client closes the stream channel. After this timeout, the stream URL is no longer valid, and a new subscription must be created.
  • A subscription is deleted if the client does not open a stream channel within two minutes after creating a subscription.
  • All subscriptions have a maximum lifetime of 24 hours after being created. When this lifetime ends, the server will close the connections to the client(s). After that, a new subscription is to be created.
  • In contrast, the lifetime of an HTTP SSE connection is not guaranteed. The connection can be dropped at any time by HTTP intermediaries, according to their rules. In such cases, the subscription will be available for a reconnection for two minutes, via an existing stream URL.
Language
Click Try It! to start a request and see the response here!