i have once again found an issue that could've been detected early by the developer introducing artificial latency to the SQL database