Jamil 4d43d2cb77 fix(portal): trigger email for Okta 4xx errors (#10578) ...

When Okta returned a 4xx status code from the API, we had updated error
handler to grab the errors from body or headers and return these.

However, the caller was expecting an explicit empty string for 401 and
403 errors in order to trigger the email send behavior.

Since that wasn't being matched, we were logging the error internally
only, and continuing to retry the sync indefinitely without sending the
user an email.


Fixes #8744 
Fixes #9825

2025-10-16 15:10:04 +00:00

..

api

chore(portal): remove Jason in favor of JSON (#10550)

2025-10-13 17:39:53 +00:00

domain

fix(portal): trigger email for Okta 4xx errors (#10578)

2025-10-16 15:10:04 +00:00

web

build(deps): bump floki from 0.37.1 to 0.38.0 in /elixir (#10585)

2025-10-16 15:09:50 +00:00