'Abort Delayed Actions on a trigger' not working as expected #3396
-
|
I'm looking for a little help understanding aborting delayed actions on a trigger, (I have previously successfully used the abort on a button, so am wondering if this might be a bug?) I was attempting to introduced a functionality whereby my Stream Deck would return to a specific 'home' page after (say) 10s of no button presses. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
hmm. This is a use case I hadnt considered. I think what is happening is that the 'abort delayed actions on a trigger' is finding the current execution of actions and aborting it. |
Beta Was this translation helpful? Give feedback.

As far as I see it, the workflow of CrispedToast worked with the old style delays. I think with the new wait action it would be better to rename the existing
abort delayed actions on a triggeraction toabort trigger runsand also for the buttonsabort button runsand that would then abort all executions of the referenced trigger or button if it is referencing a named trigger/button. The optionCurrent Triggershould be renamed toCurrent Trigger: except this runand reflect that old behaviour. We could then add the optionsCurrent Trigger: this run onlyandCurrent Trigger: all runs. Same for buttons.Especially with the if/then/else logic the "this run only" will be useful.