We rolled back the problematic code and the incident is now solved.
No components marked as affected
Resolved
Identified
The UI error was caused by a graphQL issue. A fix is being implemented. There is no impact in our DB, just the dashboard UI.
·