Changes made on AI rule not displayed in rule's name

[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: v9.4.41-0
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: #95875
Email or phone of affected tester (no customers): -
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Ventura / Chrome
App Component: Other

Action Performed:

Precondition: workspace with Rule feature enabled.

1. Go to Rules > Agents tab
2. Click on Add AI rule button
3. Select rule from suggestion list (e.g. 'Reject reports whose total is over $2,500.')
4. Click Next
5. Edit rule (e.g. change default amount)
6. Click on Create rule
7. Open added rule
8. Change amount again > Save

Expected Result:

New amount is displayed in rule's name.

Actual Result:

Old amount is displayed in rule's name.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

To be added by Applause Leads

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7213456

[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/0b720a5fde740f9f3f48e44752573d1ddc7091d6ffb56668de2ef5c121ade301

[melvin-bot]

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

[melvin-bot]

I can't run change requests for your access level. I can investigate, or file an issue in Expensify/Expensify instead.

---

Failed after 0s · 0 tools used · view debug log

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

[lanitochka17]

dupe #96640