Yes, this is the one circumstance I explained that Ignition will set the quality itself.
It seems they have somehow, but figuring out how or why may be difficult.
You should be able to get a log export from your Ignition gateway that may contain clues if we're lucky.
Again - is this out occurring right now or have you already corrected it? If it's occurring now we can try to view the server diagnostics using UaExpert, track down the Session entry from Ignition's client, see which subscriptions exist and which one has the monitored item you highlighted, then see if there is still traffic between Ignition and the server for those subscriptions.
edit: and FWIW, you are not looking at the same tag in UaExpert as you are in Ignition, at least in your screenshots.