Why do I need to re-upload FIT files after refresh?

FIT uploads used during calibration are treated as workspace scratch data, not as durable cross-device files.

That means some calibration workflows can recover a local derived snapshot after refresh, but not every action can keep using the original uploaded FIT bytes forever.

What this means in practice

  • the same browser can often restore a derived calibration snapshot after refresh
  • saved calibration profiles can preserve the settings you chose
  • raw FIT files are not synced across browsers or devices
  • some validation, residual, or export actions may require re-upload after refresh

Why this happens

TRIPS treats FIT ingest as local browser workspace data rather than a cloud file-storage workflow.

So when a later workflow needs access to the original uploaded bytes, you may need to upload the files again in your current session.

Working rule

Treat FIT ingest as session-local working data.

Treat saved calibration profiles as the durable part of calibration.

If a workflow depends on the original FIT bytes, assume re-upload may be required unless you uploaded those files again in the same browser session.

Still need help? Send a Little Note to Backpacking Light Send a Little Note to Backpacking Light