Onboarding tasks - Duplicate tasks are created in Concierge when creating workspace

[mitarachim]

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: v9.1.51-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught during regression testing, add the test name, ID and link from TestRail: #60997
Email or phone of affected tester (no customers): expensify416+da2@gmail.com
Issue reported by: Applause Internal Team
Device used: MacOS Chrome, Desktop
App Component: Other

Action Performed:

1. Sign up with a new account A > Click Skip button > Track and budget expenses > Add name > Continue
2. Add email you have access to in Enter your boss's email > Start a test drive > click Create button
3. On another chrome profile, sign up with the email address you have entered as your boss's email (Account B)
4. [Account B] Create a workspace
5. [Account B] Navigate to Concierge chat

Expected Result:

There shouldn't be a duplicate Create a workspace and Take a test drive tasks in Concierge chat

Actual Result:

There is a duplicate Create a workspace and Take a test drive tasks in Concierge chat

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6840641_1748034041349.Screen_Recording_2025-05-23_at_11.48.20_at_night.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @bfitzexpensify (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.

[melvin-bot]

Triggered auto assignment to @marcaaron (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

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

[github-actions]

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

[marcaaron]

Expected. This only happens because you are using a + testing email.