[$250] Rule - Offline deleted rules reappear after reconnecting until cache is cleared

[jponikarchuk]

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: V9.3.24-1
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #81514
Email or phone of affected tester (no customers): dreamnitethedragon@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redminote 10S Android 13
App Component: Workspace Settings

Action Performed:

1. Launch app
2. Create Workspace
3. Enable rules
4. Create a merchant rule selecting a category
5. Go offline
6. Delete the rule
7. Create another rule
8. Delete the rule
9. Duplicate the workspace
   10.Open rules
10. Go online
11. Note merchant deleted is cleared
12. Go offline
13. Note merchant deleted is shown in strike through again
14. Go to troubleshoot and clear cache
15. Go to rules
16. Go offline
17. Note now deleted merchant rule is not shown in strike through

Expected Result:

Merchant rules deleted while offline should remain deleted after going online.
Deleted rules should not reappear in strike-through state when going offline again.

Actual Result:

Merchant rules deleted while offline initially appear as strike-through (expected pending deletion state).
After going online, deleted rules are cleared from the Rules list.
When switching back offline, previously deleted rules reappear in strike-through state.
Only after clearing cache does the deleted rule stop reappearing offline.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

1.mp4

View all open jobs on GitHub](https://github.com/Expensify/App/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+Wanted%22)

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022025163014248778534
• Upwork Job ID: 2025163014248778534
• Last Price Increase: 2026-03-16

[melvin-bot]

@JS00001 recently merged #81514, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

Triggered auto assignment to @mallenexpensify (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]

Triggered auto assignment to @JS00001 (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.