Hi @Auth0.user ,
Apologies for any confusion here!
Looking at the doc I shared on error / custom error pages, these are served when there is an error during the authentication, like incorrectly formed /authorization request / invalid callback URL or an expired login link in case of a Classic Login Page instead of correctly handled login rejection due to a user being blocked.
The specification I shared regarding setting a path for the callback URL root/what_comes_next was in case you decide to try the mentioned before workaround, just I see now the link has not been attached (basically it refers to not to block a user causing a login rejection but to use actions based on a usermetadata value).
But whenever you find the specification / docs are in contradiction to what you observe, reaching out directly to the repo owners seems to be most efficient way.