There are no visible errors at all neither in Chat or BugSack. Actually there is one error at the login only that it goes away if I reload but you said isn't related to GSE already so I'm ignoring it (paste it below). Tried to Export all my macros, uninstall GSE (also removing GSE.lua variables), reinstall it, import the macros again and did not work. What did work was coming back to version 2.6.27. With that version I can import again, save current macros, everything. So unless I'm doing something wrong I really don't know what to do.

7x GSE\API\Statics.lua:84: script ran too long
[string "@gse\API\Statics.lua"]:84: in function value' [string "@GSE\API\Translator.lua"]:95: in function ProcessVariables'
[string "@gse\API\Storage.lua"]:698: in function ProcessSequenceVariables' [string "@GSE\API\Storage.lua"]:789: in function OOCUpdateSequence'
[string "@gse\API\Events.lua"]:427: in function `?'
[string "@ace3\AceTimer-3.0\AceTimer-3.0-17.lua"]:55: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:50>

Locals:
itemLink = "|cffe6cc80|Hitem:158075::::::::50:103::11:4:6316:4932:4933:1566::::|h[Heart of Azeroth]|h|r"
(*temporary) = "player"
(*temporary) = 2
(*temporary) = "script ran too long"
GSE =

Here is one thing I haven't tested and I'm going to do it and update this issue. Will reinstall latest version, 2.6.28 and after login into the game, reload to get rid of the error I mentioned above that only happens at the login and see if I can import new macros and/or save any current ones.

I have 490 enabled addons. I could try disable one by one until I find the culprit if I can do that and keep reloading however because the problem only happens at the login it will be really annoying to exit the game and come back until I find which one is causing the issue.

I use 490 Addons for more than 5 years...I did not start using them yesterday, last week or last month...Normally my FPS is
around 100 and even on Raids only goes down to 90-95 so I don't think that's the issue. I believe in your first explanation that one particular Addon should be causing this issue since you're 100% isn't GSE.

Here is my computer specs

CPU: Intel Core i7-9700K 3.6 GHz 8-Core
Cooling: Noctua NH-D15 CHROMAX.BLACK 82.52 CFM CPU Cooler
Motherboard: Asus ROG MAXIMUS XI HERO (WI-FI) Intel Z390
GPU: Sapphire Radeon RX 5700 XT 8 GB NITRO+ SE
Memory: G.Skill Trident Z RGB 64 GB (4 x 16 GB) DDR4-3200
Storage: Samsung 970 Evo Plus 500 GB M.2-2280 NVME
Storage: Samsung 970 EVO Plus 2 TB M.2-2280 NVME (WoW is here btw)
Storage: Samsung 860 Evo 2 TB 2.5" SSD
Monitor: ASUS ROG Strix XG32VQ 31.5-Inch Screen LCD Monitor (XG32VQ)
Case: Cooler Master MasterCase SL600M ATX Mid Tower
PSU: Corsair RMx 1000 W 80+ Gold Certified Fully Modular ATX Power Supply
OS: Windows 10 Pro

I believe you when you say isn't GSE...not saying otherwise. I use GSE since was launch and never had this issue before so I'll go ahead and do I wish would not deed which is disabled one by one (maybe a group of 10-20) until I found the culprit :-)

I wonder if could be a a single old macro in GSE that is causing this. If I save/backup the GSE.lua variable and then remove it the GSE will come up without any of my macros right?

UPDATE: The error at the login is the one causing the issue. After reinstalling the version 2.6.28, just after the login I wasn't able to save, import or do anything however reloading fixes the issue. I really don't know what do now to get rid of that error besides reloading every time after login. Good news is that I know now how to fix it.

I cannot replicate your error nor can I make it fail in saving macros in either Retail or Classic on either of the versions you have listed.

Here’s the only change between those versions:

#726

All it does is add a blue punch card to the editor so you can test the output of a variable. It has no impact on saving or editing macros in any way.

All that leaves for me to go on is if there is another mod that is conflicting with GSE.

Btw a “Script ran too long error” can be caused by any mod. There is a generic amount of time that all mods have to complete within. They all run in the same pool but it reports the mod that was last executing as the “fault”.

The other thing to potentially look for is a bad “variable” in a mod that is not resolving in time.

Yes if you backup and remove the GSE.lua file from the WTF directory - no macros will load in.

Closing as no new information.