Skip to content

Settings-Changing copilot access to limited shows oops something went wrong. #107514

Open

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: V9.5.47
Reproducible in staging?: Yes
Reproducible in production?: Unable to validate in Prod - Provide reasoning.
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #105894
Email or phone of affected tester (no customers): dreamnitethedragon+vegst@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redmi note 10s android 13
App Component: User Settings

Action Performed:

  1. Launch app
  2. Go to settings - agent - add an agent
  3. Go to copilot
  4. Under members can access your account, tap on 3 dots next to agent user
  5. Tap change access level - Limited

Expected Result:

Changing copilot access to limited must not show oops something went wrong.

Actual Result:

Changing copilot access to limited shows oops something went wrong.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7319725_1795154469477.Screenrecorder-2026-11-20-11-25-46-233.mp4

View all open jobs on GitHub

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

Activity

  1. applause-bot commented on Nov 20, 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/abc610c0a5fa990c61f65723ba6a5e396fc8ff5d731f06b44a3cab0e65aa7ea2

  2. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 20, 2026
  3. expensify-chore-bot commented on Nov 20, 2026

    @expensify-chore-bot

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

  4. expensify-chore-bot commented on Nov 20, 2026

    @expensify-chore-bot

    @Julesssss @Ollyws @dylanexpensify you have been assigned to this deploy blocker because you reviewed the offending PR: #105894

  5. expensify-chore-bot commented on Nov 20, 2026

    @expensify-chore-bot

    @hungvu193 you have been assigned to this deploy blocker because you authored the offending PR: #105894

  6. expensify-chore-bot commented on Nov 20, 2026

    @expensify-chore-bot

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

  7. github-actions commented on Nov 20, 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.
  8. hungvu193 commented on Nov 20, 2026

    @hungvu193
    Contributor

    🥶 Ooops, I forgot we can copilot agent. Checking

  9. MelvinBot commented on Nov 20, 2026

    @MelvinBot
    Contributor

    🤖 Web test steps verification results: ❌ fail

    Web verification was blocked by a blank page and suspended testing session; the reported failure could not be reproduced or ruled out. The deploy-blocker investigation identified Allow downgrading copilot without magic code as the strongest suspect, but the exact API rejection remains unverified.

    Blank web page blocking reproduction

    Step Status
    1. Settings → Agent: add a personal agentBlocked: the browser displayed a blank page, and the testing session remained suspended after retry. Checkout version was 9.5.49-0; the running version could not be confirmed.
    Blank web page blocking reproduction
    ❌
    2. Open Copilot and the agent’s three-dot menuNot reached because the application was inaccessible.
    ❌
    3. Change access level → LimitedNot reached; no UpdateDelegateRole response was captured.

    Code findings: Personal agents start as Full copilots (Agent.ts:159–184). The suspected PR changes Full → Limited to immediately submit the update without a validation code and return to Copilot (UpdateDelegateRolePage.tsx:80–97). Its failure handling retains the prior role and sets the generic error (Delegate.ts:963–985), which Copilot now renders (CopilotPage.tsx:255–260).

    Release evidence: The PR was included in the reported 9.5.47-0 staging build (deployment confirmation). The inspected production source still uses the confirmation flow (UpdateDelegateRolePage.tsx:79–85).

    Confidence: Medium. This explains the changed request and matching error path, but does not establish why the request fails. An agent-specific restriction or a previously existing failure newly exposed by error rendering remains possible.

    Recommendation: Keep the deploy blocker. Reverting the suspected PR is the conservative mitigation candidate, but verify that the restored confirmation flow successfully downgrades the agent before declaring resolution. Capture the failing API response and compare personal-agent and human-copilot downgrades before choosing a forward fix. Do not merely suppress the error: failed downgrades can leave Full access unchanged. No code or GitHub state was changed.
    ❌

    view run · no recording available

  10. added
    InternalRequires API changes or must be handled by Expensify staff
    and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Nov 20, 2026
  11. hungvu193 commented on Nov 20, 2026

    @hungvu193
    Contributor

    Demoting since this also happening on Prod. Please check this comment.

    But we still need to validate an account before allowing them to change the copilot access. I'm working on a fix now.

  12. dylanexpensify commented on Nov 20, 2026

    @dylanexpensify
    Contributor

    @hungvu193 but they don't need a validate code for going from full to limited right? That was the intent of the original PR right?

  13. hungvu193 commented on Nov 20, 2026

    @hungvu193
    Contributor

    @hungvu193 but they don't need a validate code for going from full to limited right? That was the intent of the original PR right?

    Yes if they're validated account. If they aren't validated yet. They still need to validate their account first

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringInternalRequires API changes or must be handled by Expensify staffReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions