In an attempt to investigate incidents, our team is encountering the attached error. This issue is not tied to a specific workspace and is prevalent across multiple workspaces and resource groups. Is anyone else seeing a similar error or has seen it in the past ?
