If you create a macro that contains spells only available to a specific specialization (e.g. elemental), then you change spec to enhancement, all the elemental macros start throwing broken macro errors, presumably because they are trying to compile with spells you no longer know as they are specific to the specialization.

🔵 To reproduce: (Steps to reproduce the behavior)
Choose a sepcialization, e.g. Elemental Shaman
Create a macro containing an elemental specific spell, e.g. Earthquake
Save macro
Switch to Enhancement
The errors begin to display.

I think this also happens even if you just change talents to not include a spell anymore, so for example i have a PVP and PVE macro that contain different spells for different talent loadouts.

🔵 The error:
Paste the error message in this blockquote.

BROKEN MACRO AOE was unable to be programmed. This macro will not fire until errors in the macro are corrected. 
Interface/AddOns/GSE/API/Storage.lua:516:attempt to index local 'spellinfo' (a nil value)

🔵 Screenshots:
If applicable, add screenshots to help explain your problem.

🔵 Expected behavior:
Not sure what the solution would be, perhaps importing talents so the macro knows whether those talents are active? Or assiging macros to a loadout so they only try to compile with tat loadout active.. not sure on the inner workings.

🔵 GSE.lua file:
Not sure this is requried.

🔵 Desktop (please complete the following information):

• OS: Windows 11
• Game Version Retail 11.0.2.56196

🔵 GSE Version:

• Version: GSE-3.2.11
• Downloaded From: Curseforge desktop app

🔵 Additional context:
I know the addon changed a lot recently with TWW pre patch so it maybe that i missing something, but i think im doing everything correctly, please let me know if not.

p.s This addon is amazing, thank you so much!

I did just see this post: https://wowlazymacros.com/t/broken-macro-message-when-opposite-spec/42417/10 so it seems the fix is to use macros instead of spell blocks. I assume this is an API limitation? I will test and report back.

Can confirm that moving talent/specialization specific spells to macros as opposed to spells fixes the problem.

Yes this is a limitation of using the spell blocks. The spell blocks were what we may have been forced to use as to to a week before prepatch the ability for mods like GSE to use macrotext was removed from the game. Both these methods use SecureActionByttonTrmpkate from WoW’s API. The difference is that Spell blocks must be perfect always. Being in the wrong spec will throw errors. Macro blocks are only checked when they are executed so don’t have this issue.