[Due for payment 2025-10-03] [Due for payment 2025-10-01] [$250] [Duplicate policy] Better error handling when duplicating workspace fails

[mountiny]

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:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation (hyperlinked to channel name):

Action Performed:

Break down in numbered steps

1. Have a workspace where you are admin but not the owner
2. Make sure this workspace has a lot of categories and tags and members
3. Try to duplicate this workspace
4. Navigate to the duplicated workspace settings

Expected Result:

Describe what you think should've happened

When this action fails, we should show the RBR on the left had side of the settings under More features, that will clear the workspace when dismissed

Right now the error only shows in the categories:

and the requests are failing

Actual Result:

Describe what actually happened

We should add a RBR error under the more features tab that will explain the error and let the user clear it

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021968043468136655861
• Upwork Job ID: 1968043468136655861
• Last Price Increase: 2025-09-16

Issue Owner

Current Issue Owner: @CortneyOfstad

[melvin-bot]

Triggered auto assignment to @CortneyOfstad (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[DylanDylann]

@mountiny Could I help on this issue too?

[mountiny]

nothing needed right now but maybe once we will have something for you to work on

[stitesExpensify]

For the backend bug, I'm looking at the logs here

We are getting 300 which means the account already exists, but then getting an error when we try to get an authToken for that same account which is weird. I'm guessing it's because we're using the email instead of the accountID. Still digging

[stitesExpensify]

Okay so the issue is actually this line combined with this change https://github.com/Expensify/Web-Expensify/blame/main/_libfop.php#L476.

CreateAccount doesn't return email if it returns a 300.

[stitesExpensify]

I don't actually thing that is the issue :/ We do always get an email even if it is not from the command directly.

It is also not a problem with the primary email vs secondary email. I think I need to find some more logs

[melvin-bot]

@CortneyOfstad, @narefyev91, @stitesExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!