A specific keyboard shortcut trigger with advanced condition stopped working from the last one or two version (including alpha). It does not work/not triggered unless the "Advanced Conditions..." window is opened. If I remove the conditions - still the same. Here's the config:
This was one of the first triggers I've setup and it was working till now, I have not changed anything related to it.
Version: 5.250 (2025030306)
mhh there hasn't been a change in this area for some time (especially not in the last few alphas). Does the shortcut show up in recently used?
No, that's why I've mentioned "It does not work/not triggered".
Is that shortcut defined globally or in some CAG / App Specific?
Globally
Could you try setting up some basic action that just shows a hud with that variable?
It is a very fundamental variable that is used everywhere in BTT, so it should break almost everything if it was wrong. Maybe some script does override the variable?
I think I found the issue, the same trigger was configured in a CAG, however it is disabled. I think the explanation is here - Shortcuts only works if created under specific app not under "For All Apps" - #2 by Andreas_Hegenberg
Please excuse me for this, I forgot that I've disabled this shortcut in that specific CAG which resulted in that behavior.
Ah yes, that makes sense! Thanks for the update!
Do you think it is worth including something like a WARN message or similar to notify the user that this shortcut is configured somewhere else, no matter that it is disabled etc.?
Most of my shortcuts are configured many times so I would always have warning messages everywhere.
Maybe once I get to implement a real search I could add something like "find all places where this shortcut is configured".
One thing I will add soon is a better warning when disabling shortcuts in a specific app or CAG.
@xidiot Unfortunately, I often have this problem. If you test a lot and want to keep these tests, you disable them and forget about them. 
I have recently moved all tests to a “test preset” that can be activated or deactivated. It's not ideal, but it's better.
Good idea, thanks @Frank1
