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
[$250] Track - Unexpected error deleting this expense appears when categorize expense #72379
changed the title [-]Track - Unexpected error deleting this expense appears when categorize expense[/-][+][$250] Track - Unexpected error deleting this expense appears when categorize expense[/+]on Oct 14, 2025
@lschurr, should we put this on hold or close it out based on #72555?
We discussed in this Slack thread whether it still makes sense to keep the track flows in NewDot, given that we're adding the Support for unreported expense in NewDot. We though about removing them, given that the beta is only enabled for Applause and deploy blockers keep coming. We decided not to completely remove the functionality, but disable them until we’ll likely come back to the track case sometime soon.
Activity
melvin-bot commentedon Oct 11, 2025
Triggered auto assignment to @lschurr (
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.mukhrr commentedon Oct 11, 2025
@lschurr what is detailed expected behavior here? We move expense to default WS after clicking Categorize ?
mukhrr commentedon Oct 11, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
When trying to categorize unreported expense we get error.
What is the root cause of that problem?
Wheb categorizing we are trying to get report policy id from unreported expense which is logically wrong.
App/src/libs/actions/IOU.ts
Lines 6395 to 6398 in 0400484
As there is no report for expense, we make its
policyIdFAKE. And sending fake policy id causes the error from BE:What changes do you think we should make in order to solve the problem?
We need to give
policyIdof workspace on top whenchatReportdoesn't have realpolicyId.What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
N/A
What alternative solutions did you explore? (Optional)
I think there will still be a bug from BE side even after our fix. It responses with error preventing user from expected behavior:
[-]Track - Unexpected error deleting this expense appears when categorize expense[/-][+][$250] Track - Unexpected error deleting this expense appears when categorize expense[/+]melvin-bot commentedon Oct 14, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021978153473233190254
melvin-bot commentedon Oct 14, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @QichenZhu (
External)melvin-bot commentedon Oct 20, 2025
@QichenZhu Huh... This is 4 days overdue. Who can take care of this?
32 remaining items
QichenZhu commentedon Nov 26, 2025
mvtglobally commentedon Nov 30, 2025
Issue not reproducible during KI retests. (Third week)
melvin-bot commentedon Dec 2, 2025
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
melvin-bot commentedon Dec 4, 2025
@QichenZhu 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
QichenZhu commentedon Dec 4, 2025
melvin-bot commentedon Dec 9, 2025
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
melvin-bot commentedon Dec 9, 2025
@QichenZhu Eep! 4 days overdue now. Issues have feelings too...
lschurr commentedon Dec 10, 2025
Going to close this one for now