[Due for payment 2025-09-02] [$250] Failed export RBR remains in Inbox after disconnecting from accounting system

[m-natarajan]

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.1.88-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @JmillsExpensify
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

1. Create a workspace, connect to an accounting system
2. Do something that causes the export to fail (change credential, etc.)
3. Report shows up as a failed export in the Inbox
4. Disconnect from the accounting system

Expected Result:

The RBR should be removed automatically since there’s no longer an active accounting connection or any report to export.

Actual Result:

The RBR remains stuck in the Inbox, despite the accounting system being disconnected.

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021952314580992884254
• Upwork Job ID: 1952314580992884254
• Last Price Increase: 2025-08-04
• Automatic offers:
• nkdengineer | Contributor | 108400274

Issue Owner

Current Issue Owner: @laurenreidexpensify

[melvin-bot]

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

Job added to Upwork: https://www.upwork.com/jobs/~021952314580992884254

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @suneox (External)

[cosmicvulpes]

Proposal

Please re-state the problem that we are trying to solve in this issue.

What is the root cause of that problem?

1. When an export fails we mark the report with hasExportError and/or add an INTEGRATIONS_MESSAGE action.
2. Disconnecting a connection (API command RemovePolicyConnection) only deletes the connection details.
   It does not clear the hasExportError flag or the integration-message action that was created when the export failed.
   The client keeps reading that flag / action and thinks the error is still relevant.
3. The client’s hasExportError() helper therefore keeps returning true, because it still finds the old flag / action, and nothing checks whether a connection actually exists.

What changes do you think we should make in order to solve the problem?

Backend

• Inside RemovePolicyConnection, find all reports for that policy where hasExportError = true or an INTEGRATIONS_MESSAGE action exists, and reset them:
  • hasExportError = false
  • isExportedToIntegration = false
• Optionally add a “Integration disconnected” history action (not shown in Inbox) to keep the audit trail.
• Add a one-time migration that does the same cleanup for workspaces already disconnected.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

NA

What alternative solutions did you explore? (Optional)

Frontend-only: In ReportUtils.hasExportError() early-return false when getConnectedIntegration(policy) is undefined or auto-sync is off.
This hides the RBR as soon as the connection is removed.
Fixes the issue for backend fix seems solid.

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[melvin-bot]

@suneox Whoops! This issue is 2 days overdue. Let's get this updated quick!