When triggering a behavior multiple times with a large delay (say 1000), the UI becomes inconsistent and leads to buggy behavior. Please check the attached screen-cast. This probably happens since the newer behaviors will be added to the event loop and executed after the second screen has loaded.
We should figure out a better way to handle such cases. Probably ignoring the triggers after the first one (not sure if there is a use case for handling all the triggers with delay):

When triggering a behavior multiple times with a large delay (say 1000), the UI becomes inconsistent and leads to buggy behavior. Please check the attached screen-cast. This probably happens since the newer behaviors will be added to the event loop and executed after the second screen has loaded.
We should figure out a better way to handle such cases. Probably ignoring the triggers after the first one (not sure if there is a use case for handling all the triggers with delay):