Cloud UI: Fix 401 error on the Project page due to stale JWT #5080
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, re-visiting a Project page can trigger a 401 error. In the error case, a stale JWT sits in the
GetProject
Query Cache and is used in a runtime request. The 401 triggers a full-screen error page.This PR does a few things to mitigate this, notably:
refetchOnMount
,refetchOnWindowFocus
, andrefetchOnReconnect
to refetch the JWT when the user re-visits the pagecacheTime
to garbage-collect old JWTsBug report in Slack