Well, I couldn't really see how a bug would effect only one user here, based on the way the dtview & action=trust;full;dt pages are parsed, I didn't see any reason on why it would not work for
only 1 user. I'd imagine the entire DT1 and/or DT2 list having an issue at the time of parsing the pages if there was some sort of bug in the code.
As I started looking at others on the archive'd page, some are explainable on why they didn't show a DT1/2 status, but I ran into EcuaMobi who also does not show any DT status on the page, and I don't really have an explanation for that one either?
I believe he should have had a status at that time also... I haven't ran into others yet, but... *shrug* I may have to accept this as some odd DT status bug from 2019 that will drive me crazy trying to think about how it could have happened.
My only guess, assuming no forum-based blacklists/bugs, would be that this was probably related to a bug we encountered back then with SQL locking records/tables while other parsers were attempting to access/update records, which may have created the conditions necessary to not be able to access
some rows/profiles that were
in use while DT status parsing was happening. Based on the way table joins happened in this process, an inaccessible record may have just dropped out of the query and not have been included, which would have left them with no DT status. I believe it was sometime in 2020 when suchmoon re-worked the locking methodology we were using to correct the intermittent locks.