Know the data boundary
A rejected backup may have the wrong structure, an unsupported version, invalid record fields, or excessive size. The .json extension alone does not establish that the contents are a valid Fastly backup.
Use the supported file workflow
Select an original Fastly export if possible. Check that you did not choose a progress image, an unrelated JSON file, or a file modified by another application.
Backup export includes the current session when present, completed history, archived sessions, journal fields, protocol, goal, and supported settings. It is readable JSON, so store the file in a destination whose access you understand.
Check the copy you actually have
The importer validates dates, goals, journal lengths, and positive optional weight. Completed history cannot contain a still-running record, and the active record cannot have a future start.
| Check | Practical meaning |
|---|---|
| Extension alone | Not enough to validate |
| Best candidate | Unmodified Fastly export |
Manage each retained copy
Do not randomly edit fields to bypass validation. Keep the original file intact and use a known valid export when available so you do not accidentally alter personal records.
Fastly is a lifestyle timer and journal. These notes explain the app and offer reflection prompts. They are not medical advice or a prescribed eating schedule.