WowAce

What version of Grid2 are you using?

 Latest

What game client version (windows or mac) and language are you using ?

 Windows

What steps will reproduce the problem?

  Being in raid (I think cross realm or not does not matter) and try to quickly retarget using grid2 frames. After few clicks it stops working for a second or two, its just like some "quick retarged prevention mechanism". Using SuF or Blizz frames this is not happening, only using Grid2 frames. It does not happen every time! In same raid group it was slow for like an hour and then suddenly stopped. I didnt changed anything, no idea why...
Did you try having Grid2 as the only enabled addon and everything else disabled?

  Yes

Was it working in a previous version? If yes, which was the last good one?

  I didnt play for some time so not sure.

Do you have an error log of what happened? If you don't see any errors, make sure that error reporting is enabled (`/console scriptErrors 1`) or install [BugSack](https://mods.curse.com/addons/wow/BugSack).

  There is no error (errors enabled). It just reacts slowly or not at all after few retargets.

Please provide any additional information below.

 No more.

Targeting is controlled by the game not Grid2. I can do nothing about this issue.

But why this issue appears clicking on grid frames only and not on shadowed unit frames or blizzard default frames? I opened them all in the same time and tried, SuF/Blizz quick as always, grid ignoring some clicks or reacts very slowly... it has to be connected somehow.

I got two grid addons opened in the same times, plus the blizzard default unitframes, tested this to see if it had any water, and to be completely honest with you, targetting the raid members to me feeled the same on every unit on every addon/default blizz.

So I'm not sure whats causing this for you individually, I'd suggest clearing out your cache and WTF folder, maybe fresh install new addons? Not sure, also check your WA, sometimes it control some of the grid/units and make them slow, I'd suggest first disabling WA and see if the problem persists.

OK, thanks for the tips. That issue appears only sometimes so it is hard to track down the root cause for me. We can close it for now!:)