Hi @niyawe, welcome to the community!
We rolled out a config change last week that caused some errors similar to this one. We’ve rolled back that change now.