-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Task - Error shows up when creating task via [] @mention <task name> pathway #34250
Comments
👋 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:
|
Triggered auto assignment to @danieldoglas ( |
Assigning @thienlnam since he's been working on this with the contributors on this functionality But I was not able to simulate this error both on DMs and group chats when inviting people that were not participants, @lanitochka17 |
I'm not sure if this is the desired behavior, but:
@thienlnam I'll let you chime in from there! |
Following because I was testing with him and I thought the behavior was weird/wrong. IMO the user2 should NOT see the task in the DM report, they should only see it in the LHN. |
Yes this is correct behavior - so let's take User A and User B
|
I tested this and this seems to be working fine for me - not able to get the failure as mentioned and neither can Daniel so going to remove the blocker |
ok but can you explain why? To me this does not make any sense. That task and conversation did not happen in the DM with user B, why would it show up there? |
It did not, but you're taking an action that requires something of someone else. Side note - going to be closing this issue since this bug doesn't seem to be happening. Happy to talk this through more in slack if needed |
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: 1.4.24-0
Reproducible in staging?: Y
Reproducible in production?: N
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: Applause - Internal Team
Slack conversation:
Issue found when executing PR #33428
Action Performed:
Expected Result:
The task is created and assigned to the mentioned user.
Actual Result:
The task is not created. Error shows up - Unexpected error create task, please try again later
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6337787_1704899132724.bandicam_2024-01-10_19-16-59-338.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: