Workspace - System messages order seems incorrect when enabling Auto-pay reports

[vincdargento]

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.3.10-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: #78504
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: MacBook Air 15.7.3 Chrome, iPhone 15 iOS 26.2
App Component: Workspace Settings

Action Performed:

1. Sign in to ND with a new Gmail account, validate it
2. Create a workspace, add a bank account (Plaid 1111)
3. Scroll down to the Advanced section in Workflows and enable Auto-pay reports, upgrade the workspace if needed
4. Disable and enable the toggle again
5. Open the #admins room for the workspace, navigate to the system message thread

Expected Result:

The correct system message order should be: 1. enabled auto-pay approved reports 2. set the auto-pay approved reports threshold to "$100.00"

Actual Result:

When enabling Auto-pay reports toggle, the system messages are displayed as: 1. set the auto-pay approved reports threshold to "$100.00"; 2. enabled auto-pay approved reports

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @rayane-d

[melvin-bot]

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

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

[OSBotify]

Investigation Summary

Classification: Backend bug
Causing PR: #78504 - "Implement policy change log for: Rules - When enabling/disabling "Auto-pay approved reports" or when changing the "Auto-pay reports under" threshold" by @rayane-d (High confidence)
Related Issues: None

Recommendation: NEEDS INVESTIGATION

This issue requires backend investigation and a backend fix. PR #78504 only added frontend display logic for changelog messages - it did not introduce the ordering bug. The backend is creating the report actions in the wrong sequence.

Labels: Removing DeployBlockerCash as this requires a backend fix, not an App revert. Keeping DeployBlocker as the backend deploy is blocked.

Detailed Analysis

Evidence

When a user enables the "Auto-pay reports" toggle in the workspace settings, the following happens:

1. App side: The frontend calls enablePolicyAutoReimbursementLimit(policyID, true) which sends a single API command ENABLE_POLICY_AUTO_REIMBURSEMENT_LIMIT to the backend

   • Location: /home/runner/work/App/App/src/libs/actions/Policy/Policy.ts
   • This function sets the auto-reimbursement limit to a suggested default value ($100) when enabling

2. Backend side: The backend receives this single API call and creates TWO policy changelog report actions:

   • UPDATE_AUTO_PAY_APPROVED_REPORTS_ENABLED - to log the enable/disable action
   • UPDATE_AUTO_REIMBURSEMENT - to log the limit being set to $100

3. The bug: These two report actions are being created in the wrong order. The expected order is:

   • First: "enabled auto-pay approved reports"
   • Second: "set the auto-pay approved reports threshold to "$100.00""

   But they appear in reverse order.

Verification

PR #78504 modified these files:

• src/CONST/index.ts - Added new action type constants
• Language files - Added translations for the new messages
• src/libs/ReportActionsUtils.ts - Added message formatting functions
• src/libs/OptionsListUtils/index.ts - Added LHN preview support
• src/libs/ReportNameUtils.ts - Added thread title support
• src/libs/ReportUtils.ts - Added report name support
• Display components for rendering the messages
• Tests

Critically, PR #78504 did NOT modify:

• src/libs/actions/Policy/Policy.ts - The file that makes API calls
• No changes to API parameters or sequencing
• No changes to when or how the API is called

Root Cause

The App only makes ONE API call (ENABLE_POLICY_AUTO_REIMBURSEMENT_LIMIT). The backend is responsible for:

1. Receiving this API call
2. Creating multiple changelog report actions
3. Determining the order of those report actions

Since the ordering happens entirely on the backend, and PR #78504 only added frontend display logic for report actions the backend already creates, this is a backend bug.

The issue is reproducible on staging (version 9.3.10-0) but not in production because this is a new feature that does not exist in production yet. PR #78504 was the first to implement the changelog display for this feature.

[roryabraham]

@rayane-d can you look into this? I don't think it's so urgent that it should be a deploy blocker of any kind. Just a minor bug I suppose