Agreed @alex.newpath - the issue I have with it is that it’s an inelegant solution - I may have 20 entries at the same timestamp that would need to be processed, so while it may work for one bundle at a time, it doesn’t work for my use case. I’d need to prepend each timestamp with a unique identifier to make sure the correct ones are processed by subsequent steps, and it would be a huge headache.
Again, it’d be so much simpler if, y’know, I could just define the sleep module as X minutes, but perhaps that’ll come in a future update.