Understand FIT ingest warnings
When you select a FIT folder for calibration, TRIPS checks the folder before full processing begins.
The warnings are meant to answer a practical question:
Is this FIT folder likely to be manageable in this browser session?
TRIPS looks at:
- how many
.fitfiles are selected - the total selected FIT size
- the size of the largest FIT file
TRIPS then shows a risk level before you continue ingest:
- Low: this folder size usually ingests successfully
- Medium: ingest may take a while and may not restore fully after refresh
- High: ingest may be slow or may exceed browser memory or local storage limits
How to decide what to do
- Continue when the folder is representative and you intentionally want to try it.
- Cancel when the selection is obviously too broad or messy for a first pass.
- Start smaller when you mainly want a useful calibration rather than the biggest possible dataset.
What to do if you see High
- Continue if you intentionally want to try the full folder.
- If the browser becomes slow or unstable, try a smaller subset of activities.
- If you mainly want calibration from recent or representative outings, start with that subset first.
Why this happens
TRIPS processes FIT calibration files in the browser and stores a derived local snapshot for the current device and browser.
It is not a cloud-synced upload workflow.
That means very large or messy FIT selections can push browser memory or local storage limits.
What this does not mean
A high-risk warning does not automatically mean your files are bad.
It means the selection may be too large or too heavy for a smooth in-browser ingest session.
A good rule of thumb
Treat the warning as a workflow decision, not as a verdict on your data quality.
The best next step is often to use a smaller but more representative folder first.