WowAce

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

v3.3.11

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

Retail

What steps will reproduce the problem?

Simply loading Grid2

  
Did you try having Grid2 as the only enabled addon and everything else disabled?

Maybe a issue with Grid 2 and Enhanced Quality of Life addon

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

Yes, One version prior to the current 

v3.3.11

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

7x bad argument #1 to '?' (Usage: local result = UnitHealthPercent(unit [, usePredicted, curve]))
[Grid2/modules/StatusHealth.lua]:61: in function 'GetPercent'
[Grid2/modules/IndicatorAlpha.lua]:23: in function 'Update'
[Grid2/GridFrame.lua]:194: in function 'UpdateIndicators'
[Grid2/GridFrame.lua]:89: in function <Grid2/GridFrame.lua:81>
[C]: in function 'SetAttribute'
[Blizzard_RestrictedAddOnEnvironment/SecureGroupHeaders.lua]:210: in function <...rd_RestrictedAddOnEnvironment/SecureGroupHeaders.lua:130>
[Blizzard_RestrictedAddOnEnvironment/SecureGroupHeaders.lua]:495: in function <...rd_RestrictedAddOnEnvironment/SecureGroupHeaders.lua:394>
[C]: in function 'Hide'
[EnhanceQoL/libs/AceGUI-3.0/widgets/AceGUIContainer-Frame.lua]:125: in function 'Hide'
[EnhanceQoL/libs/AceGUI-3.0/widgets/AceGUIContainer-Frame.lua]:21: in function <...oL/libs/AceGUI-3.0/widgets/AceGUIContainer-Frame.lua:19>

Locals:
self = <table> {
indicators = <table> {
}
priorities = <table> {
}
dbx = <table> {
}
enabled = true
name = "health-current"
}
unit = nil
deadAsFullHealth = nil

Please provide any additional information below.

Update to version 3.3.14-beta

Using the beta version stopped generating bugs or errors, however it seems every so often the some of the unit frames will disappear or show that everyone in the party or raid is out of range and not clickable. It only seems to happen in combat for parties and raids. I will try to get a video, but that doesn't sound helpful without a log of the bug.

If no Lua error is showing up, this does not look a grid2 bug, grid2 does not manage the click casting and cannot change the unit frames in combat (this is a game restriction).

So even if the unit is not painted it should be clickable.

Are units in raid/party being changed/joining/leaving in combat?

Or maybe another addon or some blizzard UI element is drawing some frame on top of the grid frames blocking the click casting behavior. 

I'm using the Blizzard built in click casting. It must be some type of Blizzard UI data not being passed correctly. If I'm in combat with other addons disabled and someone dies in combat their frame  completely disappears on Grid. Unfortunate.

Other than that it seems to function correctly.

But it seems the behavior you are describing is configured in this way in your profile.

Your profile has  the health-current status linked to the alpha indicator  (the unit frame transparency). So when the player is at full health the frame is full opaque and on dead full transparent.

If you don't want this behaviour goto indicators / alpha and  remove the health-current status from the statuses list.

Verify other statuses linked to the alpha indicator, maybe there are more statuses that should not be there. Usually in the alpha  indicator you should only see: range, dead, offline, and phased statuses. 

You can try out Clique addon instead of default game click casting too. 

I will give that a shot, I have had the same profile since I created it at the beginning of the expansion from scratch. I guess its just behaving differently now but as intended.