The “Wait” action below could be very interesting for me. But it doesn't work the way I expected. Why is it necessary to specify a specific BTT trigger before anything else is executed?
Is it possible to set it up to wait for the next / any BTT trigger?
Maybe this example will clarify how this action works:
Here after pressing cmd+opt+A, the action sequence waits for a three finger down swipe. If that swipe happens, it will show a HUD.
Here after pressing cmd+opt+A the action sequence waits for a three finger UP swipe instead:
Note: this specific setup only works with > 6.349 if the "Allow Parallel Execution Instead Of Conflict Menu" option is checked. On older versions it would first show a conflict menu because we have cmd+opt+A configured twice.
It will however always require to have a trigger set up which it can wait for (in this case the two gestures that do nothing on their own)
Thanks, Andreas. So it works just as I thought it would 
It didn't work for me because I tried using two shortcuts that I had already set up but were disabled.
I know you've already explained to me that there's nothing you can do about it. And I’m sure you wouldn’t say that if it weren’t true. But this is a real problem. The more triggers you have, the greater the risk. Something just isn't working. No entries under “Recently Used.” If you don't know what to look for, you have no way of figuring out what's going on.
So if you ever do find a way to “properly” disable triggers or somehow indicate that they’re interfering with something else, that would certainly help more than just me 
