Looped event calls

[george-y-brown]

Hi - I've been looking at the performance of this tap for the event-based substreams, and wanted to check if there was a reason it looped through each guide/page/track event to call them in turn, instead of using a single parameterless call?

As far as I can tell this gives the same output but with a much quicker runtime due to the lack of looped calls - is there a reason this approach wasn't taken?

[jtilala]

Hi @george-y-brown, In the past, we have tried to make substream independent from the parent stream. We are able to get feature_events, page_events, and track_events without a parent for a dayRange period but got below error for hourRange period. So we can not make the above events-related streams independent of their parent.

We also asked for hourRange in support but Pendo support says hourRange is not supported right now. Once it is provided from Pendo, we can surely implement this.