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
IOU - Money Request and Split bill missing from LNH #22924
👋 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.
Looking at the logs we get 406 Chat report with these participants already exists with different ID
Hence I believe this is the same instance of #22663 where the issue is stemming from the fact the other user is not knownUser and hence we dont retrieve the login field for them, which is needed to find the correct chat/ or pass the correct email to the command.
I dont think this should be a deploy blocker but its something we have to resolve after the secure login migration as there is no clear plan ahead afaik. Alex B is ooo today and Puneet is out for a week so we should probs discuss tomorrow
I missed this, but now I'm able to reproduce, and I think I found a relevant error in the logs
Throwing exception with message: '406 Chat report with these participants already exists with different ID' from auth/lib/Transaction.cpp:1638
Error processing command 'CreateIOUTransaction' (406 Chat report with these participants already exists with different ID), ignoring.
Activity
OSBotify commentedon Jul 14, 2023
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
StagingDeployCashdeploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:melvin-bot commentedon Jul 14, 2023
Triggered auto assignment to @cead22 (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.cead22 commentedon Jul 17, 2023
Following the steps here worked for me. It looks like this request may have failed for @lanitochka17, I'm gonna see if I can find logs

mountiny commentedon Jul 17, 2023
Looking at the logs we get
406 Chat report with these participants already exists with different IDHence I believe this is the same instance of #22663 where the issue is stemming from the fact the other user is not
knownUserand hence we dont retrieve theloginfield for them, which is needed to find the correct chat/ or pass the correct email to the command.I dont think this should be a deploy blocker but its something we have to resolve after the secure login migration as there is no clear plan ahead afaik. Alex B is ooo today and Puneet is out for a week so we should probs discuss tomorrow
cead22 commentedon Jul 17, 2023
I missed this, but now I'm able to reproduce, and I think I found a relevant error in the logs
cead22 commentedon Jul 17, 2023
I reproduced the error in production (logs), so I don't think we need to block on this, since it also fails, even though it looks a little different
cead22 commentedon Jul 17, 2023
Closing since this is kind of a duplicate of #16105 (comment) and #22663 and it should be fixed by the same fix that addresses those