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 2026-07-23] Agents - No error when merging/closing account, device management is blank #95726
Version Number: 9.4.32-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#95421 Email or phone of affected tester (no customers):sidbhisdhidhisdhis@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.5 / Chrome App Component: Other
Action Performed:
Go to staging.new.expensify.com
Go to Account > Agents.
Click New agent and add an agent.
Click Copilot on agent row.
Go to Account > Security.
Click Merge accounts.
Enter email, select the checkbox and click Next.
Close the RHP.
Click Device management.
Close the RHP.
Click Close account.
Enter message, enter email, click Close account > Yes, continue.
Expected Result:
Error message should show up when agent cannot merge account and close account.
Device management screen should show the sessions.
Actual Result:
No error message shows up when agent cannot merge account and close account.
Device management screen is blank.
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
The two are separate roles on two different PRs, which is why the reviewer of the offending PR doesn't appear here.
Why ikevin127, not cretadn22:
The You have been assigned to this deploy blocker because you recently merged this PR: #95421 comment was aimed at yuwenmemon, who merged the offending PR (#95421) — he was auto-assigned at 16:09, then reassigned to the PR author NicolasBonet an hour later. Deploy-blocker auto-assignment routes to the merger of the offending PR, not its C+ reviewer, so cretadn22 (who reviewed Restore Wallet and other Account sections for agent accounts #95421) was never pulled in.
ikevin127 is on this issue in a different capacity: he self-assigned as the Contributor+ who reviewed the fix PR (#95812) and completed the BugZero checklist. The $250 is for reviewing the fix — unrelated to who reviewed the offending PR.
So cretadn22 = C+ on the offending PR, ikevin127 = C+ on the fix PR. The auto-assignment never considers the offending PR's reviewer at all.
Existing issue: Yes — this is exactly the gap tracked by the internal task "Deploy blocker auto-assignment: consider the C+ reviewer of the offending PR", which you filed (from Expensify/App#93498) and are assigned to. It lives in a private repo, so I can't link it from this public thread, but you're an assignee on it and it proposes routing to (or looping in) the offending PR's C+ reviewer instead of only the merger/BugZero fallback.
Activity
applause-bot commentedon Jul 9, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/d4010970064d6c7bc6cc771c3e2b862ebebfa9211ce5646d7f237660055437ff
melvin-bot commentedon Jul 9, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #95421
melvin-bot commentedon Jul 9, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jul 9, 2026
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
MelvinBot commentedon Jul 9, 2026
Run details
25 remaining items
melvin-bot commentedon Jul 22, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Jul 22, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Jul 24, 2026
@MelvinBot near the top I see
Then I see @ikevin127 was assigned by not @cretadn22 who was the reviewer on the offending PR, why?
Is there an issue that already exists to address this problem? If so, what's link .
mallenexpensify commentedon Jul 24, 2026
Payment Summary
Contributor+: @ikevin127 due $250 via NewDot
^ Test case created. Thx
MelvinBot commentedon Jul 24, 2026
The two are separate roles on two different PRs, which is why the reviewer of the offending PR doesn't appear here.
Why
ikevin127, notcretadn22:You have been assigned to this deploy blocker because you recently merged this PR: #95421comment was aimed atyuwenmemon, who merged the offending PR (#95421) — he was auto-assigned at 16:09, then reassigned to the PR authorNicolasBonetan hour later. Deploy-blocker auto-assignment routes to the merger of the offending PR, not its C+ reviewer, socretadn22(who reviewed Restore Wallet and other Account sections for agent accounts #95421) was never pulled in.ikevin127is on this issue in a different capacity: he self-assigned as the Contributor+ who reviewed the fix PR (#95812) and completed the BugZero checklist. The $250 is for reviewing the fix — unrelated to who reviewed the offending PR.So
cretadn22= C+ on the offending PR,ikevin127= C+ on the fix PR. The auto-assignment never considers the offending PR's reviewer at all.Existing issue: Yes — this is exactly the gap tracked by the internal task "Deploy blocker auto-assignment: consider the C+ reviewer of the offending PR", which you filed (from
Expensify/App#93498) and are assigned to. It lives in a private repo, so I can't link it from this public thread, but you're an assignee on it and it proposes routing to (or looping in) the offending PR's C+ reviewer instead of only the merger/BugZero fallback.quinthar commentedon Jul 31, 2026
Approved $250 to @ikevin127