WowAce

What version of Grid2  are you using (Version is displayed in General/About Tab) ?
2.8.71

What game client version, classic or retail, windows or mac and language are you using ?

Cataclysm Classic, Windows 10, DX12, Nvidia GTX1070, English. 

What steps will reproduce the problem?

I wasn't able to actually figure this out.
This is the 2nd time I've noticed this issue & the previous time it was also inside an Inferno Heroic dungeon. 
 
Did you try having Grid2 as the only enabled addon and everything else disabled?

Yes, with only BugSack & Buggrabber enabled.  

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

I automatically update, I sadly don't remember the exact date for when this first occurred. 
At least before Christmas.  

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).

No Lua error or anything from BugSack.
I did not know about the console command so did not run it. 
I have error reporting enabled. 

Please provide any additional information below.

After a reload, I had 2 party members function correctly and losing health while the rest was still not working. 
So that made me really confused. I had 2 priests, 1 of them worked fine and the other did not! 
I turned off/on Grid2 entirely, restarted the game in full & reloaded a lot of times. 
 
I'm still trying to replicate it inside a dungeon right now, but again not sure what causes this. 
Happened in Grim Batol & The Deadmines, both of the Inferno difficulty. 
Both times I was playing a Holy Paladin.  

I did not attempt to change my profile, which probably would've been wise to try.  

Try changing the update frequency option in "Statuses/Health&Heals/health-current".

Adjusted from instant to normal. 

Will let you know if this happens again, when it does what would be the best thing for me to do? 
It feels really bad to have so little data to help out with. 

Normal update frequency should fix the issue.

Instant health is faster than normal, but normal is the standard/safe option.

Instant health could display wrong information because works using a trick to guess future health changes (and the guess can occasionally fail but usually only at the end of the combat so its not very problematic), but it is like 0.2-0.5 seconds faster displaying the health changes.

Thanks!

Want me to close the ticket and open a new one when I run back into this issue?