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
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.31-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
melvin-bot commentedon Mar 4, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
[-][Domain Control] [Release 3.3] Report suspicious activity[/-][+][Due for payment 2026-03-13] [Domain Control] [Release 3.3] Report suspicious activity[/+]melvin-bot commentedon Mar 6, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Mar 6, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.31-12 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 2026-03-13. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Mar 6, 2026
Triggered auto assignment to @jliexpensify (
Awaiting Payment)rayane-d commentedon Mar 6, 2026
This is done 🎉
ahmedGaber93 commentedon Apr 26, 2026
Coming from #85528, the back button on the "Report Suspicious Activity" page doesn’t work because the
backToRouteparameter is set to the same page.App/src/pages/settings/Security/LockAccount/LockAccountPage.tsx
Line 39 in 17edfc2