We’ve found the issue was caused by a custom SQL query in a user badge. So this is not an upstream issue. Thanks.