Skip to content
Docs
foxborne.comRequest a pilot

Import statuses and fixes

Find out why a run shows Partial, Quarantined or Rejected, and fix it. Each run status, file message and clock note is listed with what it means and what to do.

How-toEvery deploymentInvestigatorMarkdown
On this page11

Each run carries one import status, and the run page adds a note when the run needs you. Most fixes come down to three moves: replace a damaged or encrypted file, bring in a missing source or align a clock.

Before you start#

  • You need the Investigator or Admin role to import a replacement file.
  • In Runs, the Needs attention filter lists quarantined and rejected runs together.
  • The run page shows one note at a time, in this order: Quarantined, Rejected, Partial, Elapsed time only, then The companion clock is not aligned.

Run statuses#

StatusWhat it meansWhat to do
CompleteThe run's sources arrived and parsed.Nothing.
ParsingThe import job is running. The runs list shows a meter and a percentage, and the run page names the current step.Wait. When parsing finishes, Import job at the top right of the run page lists each step and its time.
PartialA source is missing. Findings that depend on it are not produced, and reports list the gap under Limitations.Import the missing source, or connect the place it lands.
QuarantinedFoxborne held a file back because it looks damaged, for example a flight log that ends inside a message. Nothing from it is shown as complete.Replace the file.
RejectedFoxborne cannot read a file, for example an encrypted flight log, and stops at validation.Replace it with a file Foxborne reads.

A quarantined or rejected run shows Not parsed in the Clock column, and its Flight log topics panel reads Not parsed. The file did not pass validation.

Replace a quarantined or rejected file#

  1. Read the reason

    Open the run. The note at the top gives the reason in full, and Import job, at the top right, shows the step where the file stopped.

  2. Get a good copy

    For a truncated flight log, look for a complete copy on the SD card or your log server. For an encrypted one, ask your key holder for the decrypted .ulg.

  3. Select Replace the file

    Replace the file opens Import files. Add the good copy together with the run's other files, check Vehicle and Run label, and select Import.

If the log on the SD card is itself truncated, no complete copy exists. The run keeps its quarantine note, and its reason stays on record.

Example: a truncated flight log#

Run R-0933 in the example dataset, a survey flight on UAS-05, is Quarantined with this reason:

The flight log ends inside a data message at 41.2 MB. The file was truncated, most likely when power was cut during logging. Nothing from it is shown as complete.

A ULog is a sequence of messages, and each one states its own size in its header. A file cut off by a power loss stops partway through one.

In Import job, Validate type, size and schema and Hash originals (SHA-256) pass. Parse flight log then stops with Truncated inside a data message, quarantined, and the audit log records Quarantined file for R-0933.

Example: an encrypted flight log#

Run R-0932, a recon leg on UAS-08, is Rejected with this reason:

The flight log is encrypted. Foxborne does not decrypt logs. Import the decrypted .ulg exported from your key holder.

The job stops at its first step, Validate type, size and schema, with Encrypted log, stopped. The audit log records Rejected file for R-0932, with the detail Encrypted log.

Messages on the Import page#

These appear on a file's row before you import. A quarantined or rejected file stays out of the run.

MessageStatusWhat it meansWhat to do
Larger than the 250 MB limit. Ask an admin to raise it for this import.RejectedThe file is above the import limit. Foxborne refuses it with a reason and never truncates it.An admin raises Largest file under Settings, Import, to 1 GB or 4 GB. The message quotes the current limit.
Named .ulg, but the ULog magic bytes are missing. The file may be corrupt or not a PX4 log.QuarantinedThe name says ULog, but the first seven bytes are not 55 4C 6F 67 01 12 35.Copy the log from the SD card again. If the new copy fails too, the file is not a PX4 ULog.
Not a format Foxborne reads. Expected PX4 ULog, journalctl JSON, collector JSONL or receiver JSONL.RejectedNone of the format checks matched the start of the file.Check the file. Export a journal with journalctl -o json, not in a text format.
A text log in a format Foxborne does not read yetNew formatThe file is text with times on every line, but no parser covers it. It stays out of the run until a parser is saved.Select Propose a parser, check the parser's run over every line and save it. See Import a format Foxborne does not read yet.
The file could not be read.RejectedThe browser could not read the file to hash it.Check that the file opens on your machine, then add it again.

Partial runs#

A partial run names what is missing. These are the notes in the example dataset.

NoteRunWhat to do
No companion journal for this runR-0930Export the journal covering the run with journalctl -o json and import it.
No ground receive log for this runR-0925Import the receive log from range control, or connect the directory it is written to.
No collector on this vehicleR-0923Enroll the vehicle's collector, so later runs bring their journal units and process samples with them.
Flight log only. The collector was not reachable after this run.R-0928Check the vehicle under Sources, Vehicle collectors. A collector resumes uploading on its own when its link returns.

Clock notes#

A run can be complete and still carry a clock note. Both notes change what the timeline and reports claim about time.

Elapsed time only#

The flight log has no GPS fix, so there is no UTC anchor. Run R-0936 in the example dataset, a hangar hover, shows this note:

Indoor run with no GPS fix, so there is no UTC anchor. Times are shown from log start. Nothing on this run is shown as wall-clock time.

The run page shows wall time unknown under Started, and no track on the map. Nothing needs fixing for an indoor run. On an outdoor run, check that the GPS receiver had a fix during the flight.

The companion clock is not aligned#

chrony on the companion computer never had a time source, and the collector recorded no SYSTEM_TIME pairs. Run R-0922 reads chrony never synchronised on uas07-orin, and collector 0.7.3 does not record SYSTEM_TIME. Companion evidence is kept on its own clock.

The journal and process samples stay on their own clock. Ordering bounds between sources shows No claim for them, and the clock_uncertain rule raises a warning.

  • For this run, select Align in INC-0139, then follow Align a clock by hand.
  • For later runs, give chrony a reachable time source, and update the vehicle to collector 0.8.1, which records SYSTEM_TIME pairs.

Next#