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
[Due for payment 2025-10-15] [Due for payment 2025-10-13] Reports - "Category no longer valid" is shown briefly when moving expense #71835
👋 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.
Please re-state the problem that we are trying to solve in this issue.
Reports - "Category no longer valid" is shown briefly when moving expense, Because the logic is incorrect, try to sending the policy data instead of the category list, So the category list is not being sent correctly.
What alternative solutions did you explore? (Optional)
N/A
Result
Screen.Recording.2025-10-04.at.18.07.02.mov
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
🔄 I ran Vector1 on this deploy blocker issue and here are the top 6 possible offending PRs based on semantic similarity2:
#71190: Fix - "This report has no expenses" briefly shown in Reports after clearing cache
semantic similarity 56.4%
#71444: fix: Error is not removed from the report preview after paying an expense with empty field
semantic similarity 55.9%
#69291: Fix - Expense - Paying the expense removed the amount violation, but it re-appeared later
semantic similarity 54.1%
#71371: fix(report-paylist): prevent empty state after paying report offline
semantic similarity 48.5%
#71136: Fix workspace change
semantic similarity 48.3%
#71457: Remove Onyx.connect() for the key: ONYXKEYS.COLLECTION.POLICY_CATEGORIES in src/libs/actions/Policy/Category.ts
semantic similarity 46.2%
Please drop a 👍 (correct) or 👎 (incorrect) as feedback regarding the results.
Note
PR # and name added as text only to avoid triggering regression automation on the issues which the above PRs are addressing in case the finding is incorrect.
#71457: Remove Onyx.connect() for the key: ONYXKEYS.COLLECTION.POLICY_CATEGORIES in src/libs/actions/Policy/Category.ts
Footnotes
Vector is currently a local-only prototype stage app that uses AI embeddings to find offending PRs for a given deploy blocker issue. Because of the early stage of the app, results must be taken with with a grain of🧂. How it works: grab deploy blocker issue's OP data (title, steps, expected / actual result) and embed -> grab all deploy checklist issue PRs data (title, explanation of change, tests, changed files, AI diff summary) and embed -> calculate cosine similarity of issue embedding to each PRs embedding -> get results. ↩
Semantic similarity, when applied to embeddings, measures the similarity in meaning between different pieces of text by comparing their vector representations in a high-dimensional "semantic space". Texts with similar meanings are mapped to vectors that are close together, and this "closeness" is quantified using metrics like cosine similarity. This technology enables search engines and chatbots to find relevant information even without exact keyword matches, providing more accurate and contextualized results. ↩
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.23-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@ikevin127 / @DylanDylann@isabelastisser The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
changed the title [-][Due for payment 2025-10-13] Reports - "Category no longer valid" is shown briefly when moving expense[/-][+][Due for payment 2025-10-15] [Due for payment 2025-10-13] Reports - "Category no longer valid" is shown briefly when moving expense[/+]on Oct 8, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.26-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@ikevin127 / @DylanDylann@isabelastisser The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon Oct 3, 2025
Triggered auto assignment to @isabelastisser (
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.melvin-bot commentedon Oct 3, 2025
Triggered auto assignment to @MarioExpensify (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Oct 3, 2025
👋 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:
melvin-bot commentedon Oct 3, 2025
💬 A slack conversation has been started in #expensify-open-source
andriferry commentedon Oct 4, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
Reports - "Category no longer valid" is shown briefly when moving expense, Because the logic is incorrect, try to sending the policy data instead of the category list, So the category list is not being sent correctly.
What is the root cause of that problem?
The problem is coming from this line
App/src/pages/Search/SearchTransactionsChangeReport.tsx
Line 77 in b76a740
undefinedresultWhat changes do you think we should make in order to solve the problem?
It should be change
POLICYtoPOLICY_CATEGORIESlike this to fix itWhat alternative solutions did you explore? (Optional)
N/A
Result
Screen.Recording.2025-10-04.at.18.07.02.mov
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
ikevin127 commentedon Oct 5, 2025
🔄 I ran Vector1 on this deploy blocker issue and here are the top 6 possible offending PRs based on semantic similarity2:
Please drop a 👍 (correct) or 👎 (incorrect) as feedback regarding the results.
Note
PR # and name added as text only to avoid triggering regression automation on the issues which the above PRs are addressing in case the finding is incorrect.
@DylanDylann Looks like this one might be coming our PR based on #71835 (comment):
Footnotes
Vector is currently a local-only prototype stage app that uses AI embeddings to find offending PRs for a given deploy blocker issue. Because of the early stage of the app, results must be taken with with a grain of🧂. How it works: grab deploy blocker issue's OP data (title, steps, expected / actual result) and embed -> grab all deploy checklist issue PRs data (title, explanation of change, tests, changed files, AI diff summary) and embed -> calculate cosine similarity of issue embedding to each PRs embedding -> get results. ↩
Semantic similarity, when applied to embeddings, measures the similarity in meaning between different pieces of text by comparing their vector representations in a high-dimensional "semantic space". Texts with similar meanings are mapped to vectors that are close together, and this "closeness" is quantified using metrics like cosine similarity. This technology enables search engines and chatbots to find relevant information even without exact keyword matches, providing more accurate and contextualized results. ↩
16 remaining items
melvin-bot commentedon Oct 6, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Oct 6, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.23-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-10-13. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Oct 6, 2025
@ikevin127 / @DylanDylann @isabelastisser The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
[-][Due for payment 2025-10-13] Reports - "Category no longer valid" is shown briefly when moving expense[/-][+][Due for payment 2025-10-15] [Due for payment 2025-10-13] Reports - "Category no longer valid" is shown briefly when moving expense[/+]melvin-bot commentedon Oct 8, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.26-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-10-15. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Oct 8, 2025
@ikevin127 / @DylanDylann @isabelastisser The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
ikevin127 commentedon Oct 10, 2025
♻️ This issue can be closed as it was a regression issue, payment will be handled in the main issue.
melvin-bot commentedon Oct 15, 2025
Payment Summary
Upwork Job
BugZero Checklist (@isabelastisser)
isabelastisser commentedon Oct 15, 2025
closing!