Hello, I have two questions.
- Does the DELAYED API key preserve the timeframe of events, i.e. are they sent to the stream in chronological order?
- Does the '.publish_time' return the time that the delayed key sent the data, or does it return the actual live time that the delayed key received the data (to later store for a few minutes before sending over).
Thank you!
EDIT: Another question, assuming it is in order, are there any updates missed in the time it takes to send? For example, live data of A -> B -> C, the delayed key won't send me A -> C right? What if A - > B occurs in the first 'batch', will there then be B -> C in the later batch (a few minutes later), or will it skip to say G -> H?
- Does the DELAYED API key preserve the timeframe of events, i.e. are they sent to the stream in chronological order?
- Does the '.publish_time' return the time that the delayed key sent the data, or does it return the actual live time that the delayed key received the data (to later store for a few minutes before sending over).
Thank you!
EDIT: Another question, assuming it is in order, are there any updates missed in the time it takes to send? For example, live data of A -> B -> C, the delayed key won't send me A -> C right? What if A - > B occurs in the first 'batch', will there then be B -> C in the later batch (a few minutes later), or will it skip to say G -> H?

