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
It is probably linked to the fact that when loading the app component operations are performed asynchronously. Indeed, some requests might still be sent after the authentication has failed due to an expired token because the user has not yet been redirected to the login page.
It might also be linked to an issue related to Feathers that should be fixed in V4.
Typical logs:
/kargo-aktnmap_aktnmap.1.npjexaglp0j97p67toq0z4roz
[31merror[39m: error: api/devices - Method: update: No auth token
/kargo-aktnmap_aktnmap.1.npjexaglp0j97p67toq0z4roz
[31merror[39m: error: api/organisations - Method: get: No auth token
/kargo-aktnmap_aktnmap.1.npjexaglp0j97p67toq0z4roz
[31merror[39m: error: api/5df0d2202447000024a82d44/event-logs - Method: find: No auth token
The text was updated successfully, but these errors were encountered:
It is probably linked to the fact that when loading the app component operations are performed asynchronously. Indeed, some requests might still be sent after the authentication has failed due to an expired token because the user has not yet been redirected to the login page.
It might also be linked to an issue related to Feathers that should be fixed in V4.
Typical logs:
The text was updated successfully, but these errors were encountered: