-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random messages displayed in LHN and unable to discard #44693
Comments
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
Triggered auto assignment to @sonialiap ( |
Triggered auto assignment to @jasperhuangg ( |
Tagging this issue #44683 as per this comment https://expensify.slack.com/archives/C05LX9D6E07/p1719853583621449?thread_ts=1719842019.363059&cid=C05LX9D6E07 |
I'll take this one @jasperhuangg, I'm pretty sure I know why the expense report related ones are notifying. |
When Kortney copilots into accounting@expensify.com and exports expense reports to our accounting integration, it generates two report actions with the same exact timestamp:
|
|
One solution could be to include a clause in that query to only include report actions whose
|
Here it is with all of them excluded:
|
Not sure why this didn't close since the PR was deployed to production five hours ago and the email script was definitely run. Weird. I have reached out to @kortneywynn and asked that she ping me the next time she copilots into accounting@expensify.com and exports expense reports. Will follow up here once that happens and hopefully put this issue to bed for good. |
@deetergp, @sonialiap Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Looks like latest investigations are in this thread: https://expensify.slack.com/archives/C05LX9D6E07/p1722550695230219?thread_ts=1722533224.423589&cid=C05LX9D6E07 |
Yes, @muttmuure 👍 The tl;dr is that accounting@expensify.com exported ~500 reports yesterday and some of them did become unread for a few users. I looked into the ones Puneet & JMills had gotten and the good news is that each of their lastReadTimes were updated on the back and as appropriate. The bad news while we found proof in the logs that we were queueing their last read times to go out as onyx updates in Pusher, for whatever reason, the updates did not make it to their NewDot clients, so the reports became unread when they received the EXPORTINTEGRATION system message. |
It looks like the latest PR finally took care of this issue. I think we can finally close this one out 🎉 |
Wooo! |
We unfortunately had to revert the PR that fixed this issue because adding @puneetlath and I are investigating alternative ways to fix this issue in a way that does not break things or cause other issues. |
Triggered auto assignment to @joekaufmanexpensify ( |
@joekaufmanexpensify I'm OOO Aug 19-30, adding leave buddy. |
Sounds good! Also @deetergp do we expect the fix for this to be entirely in auth? If so, I wonder if this even needs a BZ, as there wouldn't really be any payment we'd be processing. |
Still pending input from Scott |
Auth PR was deployed. Just pending input from @deetergp on if this one is now all set. |
I might still be seeing this with workspace chats that were created by setting a preferred domain group: |
Interesting. I see discussion of another issue in that thread. You think it might be related to this instead? |
Also, as an fyi, I am now also OOO until Monday. I don't think this needs a tertiary BZ member as there is no frontend PR(s) here. So should be nothing for BZ to do while I am out. Please bring to slack if that proves to not be correct. |
I'll be diving back into this today. |
Sounds good. So there are more PR(s) left for this one? |
There are not currently any PRs pending, but Matt just got hit with a bunch of unreads in his LHN, so there may be some soon. |
I think we're going to create a new issue for the latest batch that have popped up. Let's go ahead and close this one. |
Sounds good. TY! |
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?: Needs Reproduction
Reproducible in production?: Needs Reproduction
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: @coleaeason
Slack conversation: https://expensify.slack.com/archives/C05LX9D6E07/p1719842019363059
Action Performed:
Expected Result:
Messages displayed in LHN as per priority mode
Actual Result:
Random messages displayed in LHN and unable to discard it
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: