Warning Messages

What Cordelia's orange console lines mean, and why it keeps going anyway.

The messages below are taken directly from Cordelia's source code, the same way the full field reference is, and are current as of the version available on the Installing (or Removing) Cordelia page. In the app itself, these now appear in whichever language Cordelia's interface is set to. See The Console Panel for the one exception (a few crash messages that stay in English on purpose). They're shown here in English to match this page.

Why Cordelia warns instead of stopping

Cordelia's main job is reading large batches of your own .FIT files into a database that's cheap to regenerate. Because of that, it generally prefers finishing the job over stopping at the first sign of trouble. A problem with one file, or one table, gets logged as a warning and the rest of the operation continues. See Error Messages for the smaller set of problems serious enough that Cordelia stops instead.

In the console panel, warning lines appear in orange so they're easy to spot without derailing a run that's otherwise working fine.

Import warnings

MessageWhen you'll see itWhat it means
Not a valid FIT file: <file> Importing files or a folder The file doesn't look like a .FIT file at all. It's skipped entirely, and the rest of the batch continues.
Import failed for <file>: <detail> Importing files or a folder That specific file failed to import for the stated reason. The rest of the batch continues.
<N> of <M> files imported, <K> failed — see console End of an import Summary line for a batch where at least one file failed. Scroll up in the console to see which files and why.

Export warnings

MessageWhen you'll see itWhat it means
Skipped table "<name>": schema does not match the expected record type (<type>). Exporting to XLSX, JSON, or CSV A table in the database doesn't match what Cordelia expects for a table with that name. It's left out of this export, but the data stays in your database untouched.
Unexpected table "<name>" found and ignored. Exporting to XLSX, JSON, or CSV The database contains a table Cordelia doesn't recognize, for example one added by another tool. It's ignored rather than exported.
<Format> export completed with <N> warning(s) — see console End of an export The export finished, but one or more tables along the way had a problem worth reviewing. Scroll up in the console for specifics.

Database status warnings

MessageWhen you'll see itWhat it means
<table>: unable to count rows Checking database status The row count for one specific table couldn't be read. Every other table's count is still reported normally.

See also