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?:
Reproducible in production?:
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:
Slack conversation (hyperlinked to channel name): https://expensify.slack.com/archives/C07HPDRELLD/p1747859499925439
Action Performed:
Break down in numbered steps
Not clean what are the exact reproduction steps, but so far it seems like it might be something like this:
- User is not signed in
- They go to new.expensify.com/concierge
- The sign in
- They are redirected to the concierge page using an optimistic reportID
- They add a comment
Expected Result:
Describe what you think should've happened
They should be redirected to the correct report by a result of the OpenReport call using the preexistingReportID
Actual Result:
Describe what actually happened
The comment action fails in the Concierge chat showing this error
This is very confusing as concierge as the main flow in the app and users should never hit this error with Concierge
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Select the officially supported platforms where the issue was reproduced:
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021925533573796395655
- Upwork Job ID: 1925533573796395655
- Last Price Increase: 2025-05-22
- Automatic offers:
- nkdengineer | Contributor | 107425366
Issue Owner
Current Issue Owner: @NicMendonca
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?:
Reproducible in production?:
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:
Slack conversation (hyperlinked to channel name): https://expensify.slack.com/archives/C07HPDRELLD/p1747859499925439
Action Performed:
Break down in numbered steps
Not clean what are the exact reproduction steps, but so far it seems like it might be something like this:
Expected Result:
Describe what you think should've happened
They should be redirected to the correct report by a result of the OpenReport call using the preexistingReportID
Actual Result:
Describe what actually happened
The comment action fails in the Concierge chat showing this error
This is very confusing as concierge as the main flow in the app and users should never hit this error with Concierge
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Select the officially supported platforms where the issue was reproduced:
Platforms Tested:
On which of our officially supported platforms was this issue tested:Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @NicMendonca