An unknown number of users got a blank screen after reordering elements in different tables and trying to enter some of the elements in the table (UTC-05 23-09-06 13:21 to 23-09-08 17:58 2.2 days -time to recover-). The incident was discovered proactively (at UTC-5 23-09-07 10:58: 0.9 days -time to detect-) by one of our developers who was using the platform and got a blank screen when reordering the elements of the vulnerability table and then tried to enter one of the vulnerabilities and reported it internally to create the respective issue [1].
To persist the sorting preferences, the hook useStoredState was used. To work properly, this hook requires the use of the function useState, but it was never called in the code [2], causing the value to not be updated correctly. This resulted in making the preferences set in a table be set globally instead of separated by each table, so, when switching between tables, instructions were passed for attributes that existed in the first table but not in the second. This generated an error that caused the platform to return a white screen.
The permanence of the sorting was disabled [3], this way the sorting options are not being saved and the cracking is prevented from occurring. This is a temporary workaround that eliminates the blank screen bug, however, the engineering team is working on re-enabling the permanence of the sorting options.
The platform had tests that confirmed the correct sorting in the tables, however, these did not take into account a sorting persistence functionality that did not previously exist, and for which no tests were added or effectively tested manually when added. MISSING_TEST