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
{{ message }}
Repository navigation
[Due for payment 2025-09-19] [$250] Optimistic report name computation causing unexpected log out? #69175
The Optimistic report name computation PR / feature creates a middleware in the API's prepareRequest, which is likely introducing a race condition that affects authentication and other actions. This causes requests to not be properly stored in Onyx, resulting in users being unexpectedly logged out in various scenarios.
changed the title [-]Optimistic report name computation causing unexpected log out?[/-][+][$250] Optimistic report name computation causing unexpected log out?[/+]on Aug 25, 2025
I reviewed the PR. I don't think we need to run the whole QA regression test suite on it before merging, if that's what you were asking for. But we can certainly run tests ourselves on the adhoc build.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.12-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@thesahindia@RachCHopkins The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
[-]Optimistic report name computation causing unexpected log out?[/-][+][$250] Optimistic report name computation causing unexpected log out?[/+]melvin-bot commentedon Aug 25, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021960016385628235477
melvin-bot commentedon Aug 25, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @thesahindia (
External)melvin-bot commentedon Aug 25, 2025
Triggered auto assignment to @RachCHopkins (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.MelvinBot commentedon Aug 25, 2025
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
neil-marcellini commentedon Aug 27, 2025
We might fix it in this PR, or deploy it behind a very restrictive beta and fix it separately.
Reimplementation of Optimistic report names functionality
10 remaining items
sosek108 commentedon Sep 5, 2025
I've updated original PR with changes described in previous comment.
@neil-marcellini @thesahindia @RachCHopkins
can we create adhoc and ensure by QA that my fix resolves problem?
neil-marcellini commentedon Sep 8, 2025
I reviewed the PR. I don't think we need to run the whole QA regression test suite on it before merging, if that's what you were asking for. But we can certainly run tests ourselves on the adhoc build.
neil-marcellini commentedon Sep 8, 2025
The root cause has been identified, and won't be included when re-applying the feature, so this can been closed.
sosek108 commentedon Sep 9, 2025
@neil-marcellini
No, of course not. I meant that someone other by me verify if the bug is not present anymore
[-][$250] Optimistic report name computation causing unexpected log out?[/-][+][Due for payment 2025-09-19] [$250] Optimistic report name computation causing unexpected log out?[/+]melvin-bot commentedon Sep 12, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Sep 12, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.12-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-09-19. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Sep 12, 2025
@thesahindia @RachCHopkins The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]