We noticed a couple hours ago that we could no longer authenticate using the Authorization Code flow. Instead of being redirected to localhost:39507 with the authorization code so that we can exchange it for the token, we are redirected to localhost:39507 with content that looks like:
Downdetector suggests that this may be an issue on your end which you are not aware of yet, so wanted to flag in case: https://downdetector.com/status/auth0/
All of our login flows that use auth0 started failing at once and we did not make any code changes we can connect to this error recently.
Same here. It’s related to action execution so a potential workaround is to switch off any actions you have hooked up temporarily, if that is at all viable. That’s what I’ve just done on our account because we only utilise actions for adding custom claims which affect a small subset of users. If you’re not able to switch off actions then you’re probably out of luck until it’s resolved, though
Yes had that same response, can confirm rolling back fixes the issue. If Node 18 isn’t considered ready for use I’d possibly add a stronger warning to that effect on this banner - especially when shown for an action hooked up to a production flow. Appreciate the runtime is still labelled as Beta, but Node 18 in general is in LTS and is stable, so I think it’s reasonable to assume upgrading would be incident free for all but the more complicated actions. Alternatively make the upgrade process a bit more than single-click (which could be done accidentally and there’s seemingly no way to revert).
You can see the runtime listed underneath the custom action name on its page. I couldn’t find any way to rollback the version to 16 as such, instead I created a new action in the 16 runtime and copy the code across, then replace the old action in the Flow.