Pretty sure it’s not intended for a warrior to be able to charge a mob, cancel the auto and run away, just to have the mob do nothing after the charge stun. They just drop combat and never even aggro on you after the charge as long you don’t auto.
Also like I’ve said before execute is being batched twice currently. Here’s a quote from the post about it by Ekbert:
"Some background first; the way Execute works in vanilla and classic is in two stages. When you cast Execute the damage of the skill is calculated including the excess rage, the cost of the skill itself is deducted immediately (15 rage untalented), the Execute damage is applied at the next batch tick and then a server-side script runs which after a delay reduces your remaining rage to 0. Additional bug reports from warriors indicated that any rage generated during this trigger window is lost once the trigger reduces your rage to 0. For example, if your Execute cast procs Windfury Totem then the rage generated by that extra attack is not factored into the Execute damage, and is then completely lost when the trigger reduces your rage to 0.
The reason Execute feels clunky in Classic is because this trigger delay is double the size of what it was in vanilla."