I noticed something like this too.. I was trying to create a good old Sierra style boss key where all a small terminal script would turn sound off, then have BTT natively hide all windows and open Calendar. I couldn't get this to work so I added a delay and for some reason the delay seemed to come into affect during the previous action?
Postscript: I ended up rewriting the hide all windows and open/show single app part as an Applescript and it all worked fine -- no delays needed, which perhaps highlights a bigger bug somewhere in BTT?
I can confirm this issue is still there. I have tried basically the same as you: an HUD, a delay action, and something else (in my case "Sleep computer"). The HUD is shown after the delay (I've tried with blocking and non-blocking)…
I am yes. I still have a Monterey machine laying around, I can try on it if you think it might be an OS-specific issue.
I've just noticed the HUD action is the one which seems to be affected. "Show notification" action works correctly.
Other important information that may help, both HUDs from "Show when shortcut is triggered" or from the "Show HUD overlay" are affected (shown after all delays are executed).
I've just tried troubleshooting this issue and here's my finding: it may only affect long press shortcuts. The exact actions you've screenshoted don't work for me on a Keyboard shortcut with Minimum hold time set to 0.5. However, setting this to 0 solves the issue. Chances are that the issue is related to this. Can you try on your side if you can reproduce when setting Minimum hold time to something else than 0?
Yeah that's what I've read in its description. Seems to work correctly for now, even with my short delays
I already faced this issue a while ago with the Delay action (can't recall if it was also with HUD ) and didn't bothered googling, now I'll know I can fallback on this action as a workaround.