The schema definition for logs appears to be inaccurate - Auth0

Problem statement We have noticed that schema definition for tenant logs that is published in your Management API documentation shows that the response body’s scope property is of type string. However when I receive logs that have values in scope the values are always arrays of strings. I should mention that I receive these logs are processed through our custom webhook via a Log Stream. I have attached 2 screenshots to show what I’m talking about. Why is there an apparent difference

Fullstack app with TypeScript, Next.js, Prisma & GraphQL - Authentication

Build a secure web application with Platformatic, Auth0 and Next.js

Login via Auth0 does not persist · Issue #8933 · backstage/backstage · GitHub

OIDC auth method, Vault

The schema definition for logs appears to be inaccurate - Auth0 Community

Migrating millions of users to Auth0 without downtime

Introducing Single Sign-on to an existing ASP.NET MVC application - Simple Talk

Setting Up Auth0 OTP Authentication with an 8base Workspace

Suspicious IP Throttling

Health Dashboard RudderStack Docs

FAQ: Trouble logging into or accessing Amplitude – Amplitude

Connector Creation - Jitterbit's Success Central

Build a secure web application with Platformatic, Auth0 and Next.js