I can run GSE for 20 hours against a target dummy and not get this error. That leaves that there is something different between what I have and what you have in one of two areas: macro and items. If your macro is doing dumb stuff fix it. I can’t code around you having a bad macro. As an example for a place to look, In Legion there was a piece of shaman follower loot that had the same name as a shaman spell. If you were a shaman and had that piece of loot in your bag and you tried to use the spell in a macro, the follower item menu would open instead. There will be some combination of your macro and the gear you have (or don’t have) that causes this. Unless you figure out what that is I can’t solve your problem. It all comes down to fixing your macro and I can’t do that via telepathy. TimothyLuke

Then the answer is simple - fix your macro. TimothyLuke

Neither it’s a WoW problem caused by something else in your UI. GSE locking up is caused by your spells and actions locking up. TimothyLuke

I appreciate what you are saying. You can cause the problem by creating a normal macro with /cast Heart Essence. It’s an underlying WoW issue. GSE doesn’t actually DO anything. It just manages a list of macro lines and asks WoW’s macro engine to please try this line. It has no way of determining success or failure of an action. As it runs in WoW’s combat sandbox it is explicitly denied access to the parts of the API that would allow it to determine that. It’s also explicitly denied access to a lot of the exception handling because that is all outside the combat sandbox. Essentially the combat sandbox has a list of 14 or so functions that a mod can call and are essentially simple math. The exception handling we both would like to be able to do would then mean that GSE couldn’t execute any macro. When the macro is written the command is valid. And even though you don’t have a HoA it is still Valid. It’s only at execution that there is an issue however by execution it’s too late to adjust the macro. Macro Variables (#691) does however provide a macro authors a means of working around this however it does require the macro author to be aware of this. They can create a variable of say ~~HE~~. And put that as a single line in the macro with something similar to this as the value for that variable ```function () if UnitLevel("player") > 110 then return "/cast Heart Essence" end end``` If the player is > 110 then insert the cast heart essence line but if not don’t do anything on this line. This function could also check if HoA was equipped or active. As it runs outside of combat and prepares the macro for execution its feasible. It’s also reusable for whatever creates this kind of an issue with Shadowlands next week. TimothyLuke