Auth Dynamic Client Registration (DCR) Problem

Hello,

Our app was published today but we are experiencing an inconsistency between dev and published modes when using OAuth with Dynamic Client Registration (DCR) in our MCP integration.

In development mode, the system correctly calls the registration_endpoint (/oidc/register), creates a client, and uses the returned client_id in the /authorize request, so the flow works as expected.

However, in the published app, the registration_endpoint is never invoked (no DCR logs appear in Auth0), and the system directly calls /authorize with a hardcoded or stale client_id (iNyxAsfE2PBz3f73w3PoIZLm9cLLHmux), which does not exist, resulting in an Unknown client error. Both environments use the same .well-known configuration and a fully functional registration endpoint. It appears that the published connector is skipping the DCR step and using an invalid client.

Could you please help us understand why the published app is not triggering DCR and how we can reset or fix this behavior?