Skip to content

Export didn't arrive or failed

Use these steps when a rendered-report CSV does not download or a Members or Payments list job reports a failure.

A rendered report of 1,000 rows or fewer downloads as CSV immediately. A larger report is refused with a size message; it is not queued or emailed. Narrow the report filters and retry. Excel and PDF are not offered on this rendered-report path today.

Members and Payments lists have separate export jobs. Members CSV is the working download format; choosing Excel or XML currently produces CSV bytes. A Payments export’s status and download link show on the Transactions page you started it from.

  1. Check that the report has at most 1,000 rows and select Export CSV again.
  2. If the browser blocked the download, allow downloads for this site and retry.
  3. If the dialog showed Download file but it gives you no file, the CSV was built but MapleGather doesn’t yet save it at the address the link points to, so exporting again won’t help. If the dialog said “This report is too large to export” or “Couldn’t prepare the export — no file was created”, see Export a report for its three causes.

List export job failed or its file is unavailable

Section titled “List export job failed or its file is unavailable”
  1. Open Export history on the Export members page for a Members job, or the Transactions page for a Payments export.
  2. If a Payments export failed, the status line names the reason. “more than 50000 payments match — narrow the filter” means one file holds at most 50,000 payments: narrow the filters and export again. “the export could not be built” means MapleGather couldn’t build the file after several tries: export again.
  3. If a Members job is completed, select its download link; use the CSV selection for a file matching its format label.
  4. If a Payments export says “This export has expired” or “This export is no longer available”, its download link has lapsed. Export again to get a fresh file.
  • Member details missing: current rendered reports use aggregate columns. If a report offers member-detail columns, only an admin with reports:export-pii can include them.
  • CSV cells have a leading apostrophe: cells beginning with =, +, -, or @ are escaped for spreadsheet safety. The dialog cannot show a reliable escaped-cell count today. Remove the apostrophe only after checking that the value is safe to paste into a spreadsheet.
  • Members Excel/XML selection yielded CSV: use the CSV selection until the worker supports the other formats.

If the file still doesn’t arrive, nothing else on your side changes it: a rendered-report Download file link that gives no file, and a Members Excel or XML export that comes out as CSV, are both current MapleGather limits described above.