Rules - Deleted Rules reappears after go offline

[applause-bot]

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: 9.4.43-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #95312
Email or phone of affected tester (no customers): applausetester+ndk44@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Windows 11 Home/Chrome
App Component: Workspace Settings

Action Performed:

Preconditions:

• Create new Expensifail account
• Create a workspace, enable Rules

1. Open https://staging.new.expensify.com/
2. Navigate to Workspace settings
3. Navigate to Rules
4. Select Field Requirements
5. Create 2 Field Requirements rules
6. Bulk select them
7. Bulk Delete them
8. Go offline

Expected Result:

Deleted rules will not reappear

Actual Result:

Deleted rules reappear when go offline

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7215232_1784789570122.deleted_rules_reappears.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7215232

Issue Owner

Current Issue Owner: @situchan

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/2428a5e6c0b8ab67abeb5ff926f528a9d7aa02af165a096bc7606b3fedb1dcd8

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #95312

[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.

[jponikarchuk]

This issue is not reproducible when Use Staging Server is disabled