Powexec_auto (Auto-triggered powers) not working

Using both the /powexec_auto command and Ctrl+click on multiple powers on multiple trays, it's not working. It has the green circle around it and just sits there. If I click the power or use /powexec_name or a keybind it works fine.

In case it matters, this is my Inv/SS tanker. I just came out of a fight where I'd been using Dull Pain, Rage, Hasten, Unstoppable and Geas of the Kind Ones. Waiting for Unstoppable to drop, I went into Rest. After Unstoppable dropped and I recovered, I took off Rest and put Hasten on autofire to recharge. When Hasten recharged it didn't trigger.

Further testing with Rage and Foot Stomp showed that the auto-trigger wasn't working for anything but that everything else was working as it should.

Clicks work fine, keybinds work fine, slash-commands work fine for triggering. Only powexec_auto isn't working.

Edit: Yes, I submitted a /bug report also.

Edit 2: After I left the mission map it started working again.

I've had the same experience for several weeks. The control-clicked power (a wide variety of powers on a wide variety of characters) gets stuck in the "ready to fire" state. The power can be clicked to force it to fire, or sometimes it will start firing automatically again after zoning or after moving around. The power seems to get stuck often when I visit trainers and markets, and less often in a mission instance.

[ QUOTE ]
The power seems to get stuck often when I visit trainers and markets, and less often in a mission instance.

[/ QUOTE ]
Correct. If you have a non-combat NPC targeted at the time, the auto power will NOT fire. If you have an enemy targeted, or nothing, it works normally.

[ QUOTE ]
[ QUOTE ]
The power seems to get stuck often when I visit trainers and markets, and less often in a mission instance.

[/ QUOTE ]
Correct. If you have a non-combat NPC targeted at the time, the auto power will NOT fire. If you have an enemy targeted, or nothing, it works normally.

[/ QUOTE ]

I was at the end of a radio mission with nothing targeted when it happened to me.

I didn't mean to suggest that's the only time it occurs. I was just saying that you can reproduce the problem consistently by targeting a non-combat NPC (trainer, WW rep, etc).