[Due for payment 2026-08-21] "disabled submissions" system message thread header shows "turned Scheduled Submit off"

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.52-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: #97921
Email or phone of affected tester (no customers): sdsiodjnosdjiodsj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Chat Report View

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace settings > Workflows.
3. DIsable Submissions.
4. Go to #admins.
5. Right click on "disabled submissions" system message > Reply in thread.

Expected Result:

"disabled submissions" system message thread header should show "disabled submissions".

Actual Result:

"disabled submissions" system message thread header shows "turned Scheduled Submit off".

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7230476_1786394602202.7.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7230476

Issue Owner

Current Issue Owner: @mallenexpensify

[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/9812541ab473e6795d04c3accb666406323bb2379c4d598e6f16d00cc864f08b

[melvin-bot]

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

[melvin-bot]

@stitesExpensify you have been assigned to this deploy blocker because you reviewed the offending PR: #97921

[melvin-bot]

@rayane-d you have been assigned to this deploy blocker because you authored the offending PR: #97921

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

[MelvinBot]

🔍 Investigation Summary

Classification: Frontend bug (fix lives in Expensify/App)
Causing PR: #97921 - "Correct policy changelog report action system messages for: Workflows Submission frequency" by @rayane-d (Low confidence as the direct cause — see below)
Related Issues: Part of https://github.com/Expensify/Expensify/issues/668650

Recommendation: ROLL FORWARD (targeted fix)

Reverting #97921 would not fix this bug — the thread header string "turned Scheduled Submit off" comes from a completely different code path than the copy #97921 changed. The real defect is a missing case in the thread-header naming logic, so a small forward fix is required.

Assigned: @rayane-d (PR author) and @stitesExpensify (reviewer) are already assigned by Melvin; leaving as-is since they own this feature area and are best placed to roll forward.
Labels: No changes. This is a Frontend bug, so DeployBlockerCash stays. There is no DeployBlocker label to remove, and the issue is a new-feature regression (N/A on production), so removal would not be appropriate regardless.

📋 Detailed Analysis

Evidence

There are two independent code paths that render the "Submissions disabled" POLICYCHANGELOG_UPDATE_AUTOHARVESTING system message:

1. In-chat message + LHN preview — go through the dedicated frontend renderer getUpdatedAutoHarvestingMessage, which returns the translated copy updatedAutoHarvesting:

   • Renderer: ReportActionsUtils.ts L4374-L4382
   • LHN uses it: SidebarUtils.ts L1288-L1289

   PR Correct policy changelog report action system messages for: Workflows Submission frequency #97921 only edited the language strings behind this path (e.g. updatedAutoHarvesting: (enabled) => \${enabled ? 'enabled' : 'disabled'} submissions``), so the in-chat message now correctly reads "disabled submissions".

2. Thread header title — computed by computeReportName → computeReportNameBasedOnReportAction, which has handlers for dozens of POLICY_CHANGE_LOG action types but none for UPDATE_AUTO_HARVESTING. It therefore returns undefined (call + early-return L1017-L1032) and falls through to computeChatThreadReportName, which for an admin room returns the raw server message text via getReportActionText(parentReportAction) (L944-L957). That raw server text is "turned Scheduled Submit off" — a string that does not exist anywhere in the App codebase (confirmed by grep), i.e. it comes straight from the backend.

Why #97921 is not the direct cause: #97921 touched only src/languages/*.ts + two test files — it never touches ReportNameUtils.ts (the thread-header path). The header/message mismatch is pre-existing: before #97921 the in-chat message read "disabled scheduled submit" while the header already read "turned Scheduled Submit off". #97921 simply made the mismatch more obvious (and made a QA tester expect the header to match "disabled submissions"). Reverting #97921 would leave the header showing "turned Scheduled Submit off" unchanged, so revert does not resolve the reported Actual Result.

Reproducible in staging only (new feature); N/A on production.

Verification

• Affected file for the fix: src/libs/ReportNameUtils.ts, function computeReportNameBasedOnReportAction.
• Confirmed UPDATE_AUTO_HARVESTING / AutoHarvesting appears nowhere in ReportNameUtils.ts (no handler), while it is handled in both ReportActionsUtils.ts and SidebarUtils.ts.
• Confirmed action-type constant: CONST.REPORT.ACTIONS.TYPE.POLICY_CHANGE_LOG.UPDATE_AUTO_HARVESTING = 'POLICYCHANGELOG_UPDATE_AUTOHARVESTING'.
• Confirmed Correct policy changelog report action system messages for: Workflows Submission frequency #97921's file list contains only src/languages/*.ts, tests/ui/ReportActionItemTest.tsx, and tests/unit/ReportActionsUtilsTest.ts — no rendering/naming code.

Root Cause

computeReportNameBasedOnReportAction lacks a branch for the UPDATE_AUTO_HARVESTING action, so thread headers for this system message fall back to the raw backend text instead of the localized frontend copy that the in-chat message and LHN already use.

Suggested fix

Add a handler alongside the other POLICY_CHANGE_LOG cases in computeReportNameBasedOnReportAction (ReportNameUtils.ts):

if (isActionOfType(parentReportAction, CONST.REPORT.ACTIONS.TYPE.POLICY_CHANGE_LOG.UPDATE_AUTO_HARVESTING)) {
    return getUpdatedAutoHarvestingMessage(translate, parentReportAction);
}

and add getUpdatedAutoHarvestingMessage to the existing import { ... } from './ReportActionsUtils' block (it is already exported there). This reuses the exact renderer the in-chat message and LHN use, guaranteeing the header, chat message, and LHN preview all read "disabled/enabled submissions" consistently.

💡 Suggested AI code review rule

This bug is a recurring, mechanically detectable consistency gap (a new report-action message type wired into some render paths but not the thread-header path), so it may be worth a coding-standards rule so the AI reviewer catches the next one. Proposed for Expensify/App:

• Rule: CONSISTENCY-NN Wire new report-action message types into every render path
• Condition: When a PR adds/handles a POLICY_CHANGE_LOG (or other report-action) type in the in-chat renderer (ReportActionsUtils) or the LHN alternateText switch (SidebarUtils), require a matching handler in ReportNameUtils.computeReportNameBasedOnReportAction; otherwise thread headers silently fall back to raw backend text.
• Why: Missing the thread-header branch makes the header diverge from the chat message/LHN preview (this issue: header showed backend "turned Scheduled Submit off" vs message "disabled submissions").
• Search pattern: For each action-type constant handled in SidebarUtils.ts alternateText/ReportActionsUtils.ts message switches, grep the same constant in ReportNameUtils.ts; flag if absent.
• Offending code (❌): ReportNameUtils.ts L1017-L1032 (no UPDATE_AUTO_HARVESTING branch → falls to L944-L957)
• Fix (✅): add the handler shown in the Suggested fix above, mirroring SidebarUtils.ts L1288-L1289

The full rule file, with ❌/✅ code inline in App's coding-standards format, would go in Expensify/App itself. If it's worth adding, a maintainer can open it there as a draft PR.

[rayane-d]

PR:

• Fix: "disabled submissions" system message thread header shows "turned Scheduled Submit off" #98340