You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently had the following migration error, which resulted in the staging version of the app to display the No agency has been connected to this account. error message.
This one may be a bit tricky because the logic in updateAndRetrieveUserPermissionsAndAgencies sets the loadingError to true if an error was raised during the request/response, and since the loadingError was not set to true, it appears that the request went through and received a response successfully, but with no list of agencies (current assumption). We should explore a potential solution for this edge-case if one is possible on the FE.
The text was updated successfully, but these errors were encountered:
We recently had the following migration error, which resulted in the staging version of the app to display the
No agency has been connected to this account.
error message.This one may be a bit tricky because the logic in updateAndRetrieveUserPermissionsAndAgencies sets the
loadingError
to true if an error was raised during the request/response, and since theloadingError
was not set totrue
, it appears that the request went through and received a response successfully, but with no list of agencies (current assumption). We should explore a potential solution for this edge-case if one is possible on the FE.The text was updated successfully, but these errors were encountered: