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
Settings-Changing copilot access to limited shows oops something went wrong. #107514
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:
Launch app
Go to settings - agent - add an agent
Go to copilot
Under members can access your account, tap on 3 dots next to agent user
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.
👋 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.
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.
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.
❌
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).
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.
Activity
applause-bot commentedon Nov 20, 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/abc610c0a5fa990c61f65723ba6a5e396fc8ff5d731f06b44a3cab0e65aa7ea2
expensify-chore-bot commentedon Nov 20, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #105894
expensify-chore-bot commentedon Nov 20, 2026
@Julesssss @Ollyws @dylanexpensify you have been assigned to this deploy blocker because you reviewed the offending PR: #105894
expensify-chore-bot commentedon Nov 20, 2026
@hungvu193 you have been assigned to this deploy blocker because you authored the offending PR: #105894
expensify-chore-bot commentedon Nov 20, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 20, 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:
hungvu193 commentedon Nov 20, 2026
🥶 Ooops, I forgot we can copilot agent. Checking
MelvinBot commentedon Nov 20, 2026
🤖 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.
1. Settings → Agent: add a personal agent
Blocked: 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.2. Open Copilot and the agent’s three-dot menu
Not reached because the application was inaccessible.3. Change access level → Limited
Not 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
hungvu193 commentedon Nov 20, 2026
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.
dylanexpensify commentedon Nov 20, 2026
@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?
hungvu193 commentedon Nov 20, 2026
Yes if they're validated account. If they aren't validated yet. They still need to validate their account first