-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When user tries to log in to workspace after token expiration, multiple errors appear #6731
Comments
@BOHEUS Can you reproduce it to help determine the root cause of this issue? Otherwise, I think I'll close it and keep the bug in mind since it's not really actionable. Thanks for pushing Twenty! |
Sure, I'll report back when token will expire |
I was able to reproduce it on newest version of repo (mistakenly also reported it in #6732), I can't really pinpoint it in the code but it's definitely something with Apollo and useManyFindRecords like shown in the video |
@BOHEUS I can reproduce, I'm working on the sign-in / token expirations issues, will ping you back! |
I have made the fix but haven't tried this case yet. Any chance you could retry on the 0.24? |
@charlesBochet I'll check once I have some time |
@charlesBochet I can still reproduce it on 0.24 |
Ok so it's still there! Let's see if someone from the community can fix it. If not, we will take it under 0.31 release |
@ad-elias will look into this |
Fixes issue #6731 **Problem:** After access token token expires, scrolling down the `RecordTable` component will put it to an infinite loop of trying to fetch records and printing errors on every iteration. **Solution:** Disable fetching until component remount if a `FORBIDDEN` error is encountered. --------- Co-authored-by: ad-elias <[email protected]>
I'm not sure if scenario is reproducible as I didn't try to repeat it but here's what I did:
Actual: When user tries to log in to workspace with more than 1000 companies after token expiration, multiple errors appear
Screencast from 2024-08-24 17-41-14.webm
Expected: When user tries to log in to workspace with more than 1000 companies after token expiration, user should be able to log in without any problems
Note: While on video there's clearly visible that Companies are deactivated, I don't think they're a necessary step to reproduce bug.
Script: 1companies.txt
The text was updated successfully, but these errors were encountered: