Why Was My File Refused?
What each import error means, how to fix it, and why a refused file never changes your data.
Updated
A file Kaizora can’t read correctly is refused with a message saying why. A refused file never corrupts your data: fix what the message says and import it again.
“This isn’t a file of the kind chosen.”
The file isn’t the export of the source you chose, or not the part of it Kaizora reads. Check you picked the right source on Data Sources, and the right file:
- Apple Health: export.zip, or the export.xml inside it, not export_cda.xml.
- Withings: the ZIP Withings emails you, or weight.csv, height.csv, or bp.csv from inside it.
- Cronometer: servings.csv, from Export Food & Recipe Entries, not the daily summary.
- Aranet4: a CSV from Aranet Home, not an XLSX.
- Google Maps Timeline: Timeline.json, location-history.json, or Takeout’s Records.json.
- Calendar: an .ics file, not an .icbu archive.
- Bank statement: a CSV, not QFX, OFX, QIF, or a PDF.
“Part of this file couldn’t be read.”
Something in the file isn’t as its service writes it. Most often, the file was opened and saved again in a spreadsheet app, which can change its dates, numbers, or headers. Export it again from the service and import it as it came, without opening it.
“This file uses a unit that can’t be imported.”
A column is in a unit Kaizora doesn’t read yet, such as vitamin A in international units. Write to us with the column’s name.
“This file is too large to import: the limit is 256 MB.”
Only Apple Health’s export is read a piece at a time, at any size. For another service, export a shorter range of dates in several files and import each one.
The Import Stopped Partway
If an import fails or you close the page while it runs, import the same file again. What it had already written is updated, not doubled.
See What Went Wrong Later
History, at the top of Data Sources, lists every import with whether it Succeeded or Failed and its error. A source’s … menu has See history for its own.