[HOLD #93163] Export unreported to All Data IS Templates returns errors

[izarutskaya]

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

---

Version Number:
Reproducible in staging?: Needs Reproduction (unable to reproduce)
Reproducible in production?: Needs Reproduction (unable to reproduce)
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @RachCHopkins
Slack conversation (hyperlinked to channel name): expensify_bugs

Action Performed:

1. Go to
2. Go to Spend > Expenses
3. Select Bulk Expenses
4. Export > Select All Data Expense Level report

Expected Result:

Report is messages via Concierge

Actual Result:

User gets error "Hey there! Looks like your export failed to complete. Give it another try, and if it still doesn't work, let us know and we'll take a closer look."

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

Screenshots/Videos

Check the OP for the details

View all open jobs on GitHub

[izarutskaya]

Hold for the #93163 (comment)

[exfy-zapier]

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

[MelvinBot]

Issue Analysis

This is a duplicate of #91930, which is already in Reviewing with an open fix in PR #93163 — the same PR this issue is on HOLD for. Both describe the expense-level export of unreported expenses failing.

Root Cause: When you bulk-select unreported expenses and choose Export → All Data - expense level, the frontend sends its sentinel UNREPORTED_REPORT_ID (the string '0') to the backend as if it were a real report ID. The export job then tries to resolve report 0, which doesn't exist, so the backend fails the export and Concierge posts the "export failed to complete" message.

A second, related local symptom (You can't export empty report from #91930) comes from the empty-report guard at Search.ts:1148: report?.transactionCount ?? 0. For the missing sentinel report this defaults to 0, so the flow is wrongly treated as an empty report.

Evidence

• Sentinel constants: CONST/index.ts:1497-1498 — UNREPORTED_REPORT_ID: '0', TRASH_REPORT_ID: '-1'.
• These sentinels flow into QueueExportSearchWithTemplate's reportIDList via the export path in Search.ts.
• PR Fix unreported expense export payload #93163 fixes exactly this by (1) filtering UNREPORTED_REPORT_ID / TRASH_REPORT_ID out of selectedTransactionReportIDs so all-unreported selections send reportIDList: [], and (2) updating the empty-report guard so a missing report object (e.g. the absent REPORT_0) is not treated as an empty report.

The error string itself ("Looks like your export failed to complete") is a backend/Concierge message and isn't in the App repo, consistent with the export job failing server-side once it receives report ID 0.

Recommended next step: No separate fix is needed. Keep this on HOLD for PR #93163 and close as a duplicate of #91930 once that PR ships. The fix is entirely in the App frontend payload, so it'll be covered by the existing PR.

---

Next Steps: Reply with @MelvinBot <your feedback> to refine this analysis.

[melvin-bot]

Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[melvin-bot]

Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

[melvin-bot]

12 days overdue. Walking. Toward. The. Light...

[melvin-bot]

This issue has not been updated in over 14 days. eroding to Weekly issue.