Repository navigation
[CVP] Inconsistencies with sending the unread summary email to a newly invited user #48727
Description
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.0.29-7
Reproducible in staging?: Y
Reproducible in production?: Y
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: @trjExpensify
Slack conversation: https://expensify.slack.com/archives/C07HPDRELLD/p1725038167506939
Action Performed | Expected Results | Actual Results:
Case 1: Submit expense (Scan) + Message
Steps:
- Submit expense > Scan
- Send it to a new account
- Send a message right after in the DM
Expected results:
- The email is sent right away
- The unread summary email contains both the report preview and the message
- The report preview shows the receipt scanning state (as the message that follows it triggers it to send right away)
Actual results:
- Summary email takes 10 minutes to arrive
- ReportPreview is not included in the summary email
Case 3: Message only
Steps
- Start chat
- Enter the email address of a new account
- Send a message in the newly created DM
Expected results:
- The unread summary email is sent right away.
Actual results:
- The unread summary email is received 10 mins later.
Case 4: Submit expense (Scan) only
Steps:
- Submit expense > Scan
- Send it to a new account
Expected results:
- The email is sent right away after it finishes receipt scanning
Actual results:
- Unread summary email never arrives
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos/Notes
See screenshots above inline.
Note: In the development of this issue, please make sure to test this manual request case which is working correctly right now, as illustrated below.
Case 2: Submit expense (Manual) only
- Submit expense > Manual
- Send it to a new account
- Observe the email is sent upon creation
- Observe the unread summary email contains the report preview
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
melvin-bot commentedon Sep 6, 2024
Triggered auto assignment to @dylanexpensify (
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.trjExpensify commentedon Sep 6, 2024
Tagging a few peeps that I think have worked on the flows before for vis and volunteering if you can! CC: @marcaaron @blimpich @thienlnam
marcaaron commentedon Sep 6, 2024
I'd recommend we remove the case that's working as "expected" from this issue.
And break it up into 3 issues. Seems there are 3 different problems to solve and think we can parallelize this.
trjExpensify commentedon Sep 9, 2024
We could do that, but I wanted to ensure it's included and considered when testing the proposals/solutions to the other cases. I suspect the lack of considering all of these cases together is what has resulted in inconsistent results and regressions in places.
Mhm, maybe.. I think Case 1 and Case 4 are probably the same RCA with a scanned expense receipt. Case 3 is probably a different RCA, as it's a regression to the first message on chat creation not triggering the email to be sent right away anymore.
I'm a bit hesitant to split these up and have multiple people looking into overlapping (and potentially competing) changes to what is one system for delivering these emails, but I don't mind converting this into more of a tracking issue and have PRs come for whatever parts make sense to break up or something. I think we just need the one volunteer to work through these cases, personally.
melvin-bot commentedon Sep 9, 2024
@dylanexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!
marcaaron commentedon Sep 9, 2024
Can we write a QA regression test for it? It's just a bit confusing what this ticket is asking for. Not trying to criticize here. Mainly trying to think of how to make more actionable and clear tickets that people can grab and go with.
blimpich commentedon Sep 9, 2024
For case 1 & 3, I believe the summary email not being sent immediately is the expected behavior? My understanding is that we don't want to send those right away since we don't want to flood users with notifications.
Or are we saying that since they are brand new users we should be sending the notification immediately since we know they likely aren't going to have the app downloaded yet? If so I think that is a new feature, not a bug, and should probably be its own issue.
39 remaining items
jasperhuangg commentedon Oct 9, 2024
My hands are full working on the NewDot SAML Config project, and since this is becoming a fully-fledge project now with a design doc I needa to hand off the project to another engineer to avoid overloading myself.
jasperhuangg commentedon Oct 10, 2024
Hoppin back on the team here given DB's post about stopping all #expense priorities and prioritizing #convert
jasperhuangg commentedon Oct 10, 2024
@trjExpensify Do we want to close out this issue now in favor of the tracking issue?
trjExpensify commentedon Oct 10, 2024
yep!
m-natarajan commentedon Aug 21, 2026
The following test case is failing on both Android and iOS due to this issue.
Top DOWN - New user (manager) receives notification and can create new account
mountiny commentedon Sep 8, 2026
Seems like QA still noted this is happening #100479 (comment), but based on the history, it has been like that for a while. @trjExpensify should we update the test steps?
trjExpensify commentedon Sep 8, 2026
Which case exactly is failing?
mountiny commentedon Sep 10, 2026
@izarutskaya @m-natarajan are you able to help here?
m-natarajan commentedon Sep 11, 2026
@trjExpensify @mountiny Will followup and update
m-natarajan commentedon Sep 13, 2026
@trjExpensify @mountiny Archived both the test cases because of the outdated flow as per this https://github.com/Expensify/Expensify/issues/680867#issuecomment-5639723415
trjExpensify commentedon Sep 16, 2026
Thanks!