Potential issues with delay blocking

[vinceau]

Currently delays will block the list of actions. e.g. 20 second delay before clipping, and then a 10 second delay before OBS scene changing, will cause the OBS scene change to happen roughly 30 seconds after the initial event was detected.

This might not be the preferred behaviour. You can get around this for now by ordering the actions such that the action with the shortest delay happens first, and subsequent actions would set the delay to be the cumulative delay based on previous actions. e.g. set the 10 second delay for OBS scene changing first, then after that make the Twitch clip action have a 10 second delay, which would have been around 20 seconds cumulative.

Ideally it would be possible to specify whether delaying actions should block the other actions from proceeding. If it is set to not block, we could use setTimeout to trigger the action. This however would cause issues with context sharing. For example, if you expect to have access to the {{ clipID }} context variable, but the Twitch clip is set to not block, the clip ID would not be available when the action is executed.