I believe emitting an alert throws off the timing of the wait that follows it. I would like to see emitted alerts be treated as instantaneous, i.e. when the sequence activates a wait its wait is relative to the previous wait in the list, or from when the sequence started if there is no previous wait.
I found this bug after I made a 32 emit sequence, each emit being followed by a 0.4688 second wait, except for the last one. So it should take 14.5328 seconds to complete the sequence. This sequence is triggered by a 15-second repeating alert, but the last one or two emits in the 32 emit sequence aren't being triggered because the sequence starts over before getting to them. Currently only 8 of the emits actually do anything, and the ones that do only toggle visibility of one of eight layers off and toggle another one on.
TLDR I'm trying to make a sequence that repeats every 15 seconds and is divided evenly into 32 beats but I run out of time before the 31st or 32nd beat. I think the amount of time it takes to complete even an empty emit throws off the timing of the sequence. It makes more sense for a sequence to act like a timeline, with emits firing asynchronously.