Skip to content

[Due for payment 2026-07-23] Agents - No error when merging/closing account, device management is blank #95726

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


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:

  1. Go to staging.new.expensify.com
  2. Go to Account > Agents.
  3. Click New agent and add an agent.
  4. Click Copilot on agent row.
  5. Go to Account > Security.
  6. Click Merge accounts.
  7. Enter email, select the checkbox and click Next.
  8. Close the RHP.
  9. Click Device management.
  10. Close the RHP.
  11. Click Close account.
  12. 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.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7203918_1783612460655.7.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7203918

Issue OwnerCurrent Issue Owner: @mallenexpensify
Upwork Automation - Do Not Edit

Activity

  1. applause-bot commented on Jul 9, 2026

    @applause-bot
    Author

    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

  2. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 9, 2026
  3. melvin-bot commented on Jul 9, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #95421

  4. melvin-bot commented on Jul 9, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Jul 9, 2026

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. MelvinBot commented on Jul 9, 2026

    @MelvinBot
    Contributor

    ⚠️ Something went wrong. This may be a transient issue — try again. If it persists, check status.anthropic.com.

    Run details

  7. 25 remaining items

  8. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jul 17, 2026
  9. melvin-bot commented on Jul 22, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  10. melvin-bot commented on Jul 22, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/2075719479074282641/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  11. mallenexpensify commented on Jul 24, 2026

    @mallenexpensify
    Contributor

    @MelvinBot near the top I see

    You have been assigned to this deploy blocker because you recently merged this PR: #95421

    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 .

  12. mallenexpensify commented on Jul 24, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @ikevin127 due $250 via NewDot

    ^ Test case created. Thx

  13. MelvinBot commented on Jul 24, 2026

    @MelvinBot
    Contributor

    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.

  14. quinthar commented on Jul 31, 2026

    @quinthar
    Contributor

    Approved $250 to @ikevin127

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions