This guide explains what to do when an IVION Processing job fails, how to quickly triage red vs. yellow statuses, collect the right evidence, resolve common causes, and when to contact Support.
Understand the status
Failure (red): Processing aborted due to incomplete/corrupt data or a software error. Units Consumed will be empty and no units are deducted.
Finished (yellow): Processing completed but control point residuals are high or alignment is off. Units are deducted. Often resolved by fixing control points or reconfiguring them.
Quick decision tree
If status is red → Gather task details, scan logs for clear errors (e.g., BagIOException/BZ_IO_ERROR), then decide: retry upload vs. contact Support.
If status is yellow → Inspect control points and quality map; correct point configuration and re-run.
Step-by-step: What to do first
Identify the failing datasets: Open the processing job, expand tasks, and note which datasets failed.
Re-copy and re-upload the data to IVION: R-copy the dataset folder from the scanning device’s storage and re-upload it to NavVis IVION. This could fix any data compression/corruptness issues.
Download processing task details: In IVION Processing, open the job menu (three dots) and choose Download task details. This replaces the older “Download logs” action.
Check the error signature: Open the task details/attached logs and search for common patterns (see below).
Common causes and how to fix them
A) BagIOException / BZ_IO_ERROR
Typical sign of corrupted bag files during copy or upload.
Action: Re-copy data from device SSD to a local machine and re-upload to IVION.
If desktop processing: verify local storage integrity, avoid unstable network shares, and re-copy from the original media.
If the issue persists after a clean re-upload, collect task details and contact Support.
B) Finished (yellow) due to control points
Symptoms: High residuals; misaligned survey vs. reconstruction; duplicated or misnamed points.
Fix: Open View control point configuration, deselect problematic points or correct names/settings, then re-run processing. Both tasks consume units.
C) Data incompleteness or upload interruptions
Verify dataset completeness (all bag files present, expected sizes, no partial transfers).
Re-upload missing/partial files.
Collect the right evidence (before contacting Support)
Processing task details file (downloaded from the job menu).
Job link, site name, dataset IDs
Short description of what was tried (e.g., re-uploaded data, corrected control points).
Deep-dive: Where to find root cause information
Processing task details: Contains configuration, timings, and references to taskrunner/dataset IDs used to find logs.
Best practices to prevent failures
Always copy from device SSD to a stable local drive before uploading to Desktop Processing.
Avoid Wi‑Fi uploads for large datasets; prefer wired connections.
Maintain clear, unique control point naming conventions; double-check survey-to-scan associations.
Escalate to Support
When to contact Support: If a clean re-upload still fails, if yellow status persists after control point fixes, or if logs show unclear/internal errors.
Attach the processing task details file and include job link, dataset IDs, and steps already taken. Add a note to involve [Add Support Engineer] if internal routing is needed. Contact support.
FAQ
What steps should I take if my IVION Processing job fails?
First, identify the failing datasets, then re-copy and re-upload the data to IVION, and check the error signature in the task details.
How can I differentiate between red and yellow statuses in IVION Processing?
Red status indicates a failure due to corrupt data or software errors, while yellow status means processing finished but with high residuals or alignment issues.
What should I do if I encounter high residuals in my processing job?
Inspect and correct the control points, then re-run the processing to resolve the high residuals.
Is it necessary to maintain unique naming conventions for control points?
Yes, maintaining clear and unique naming conventions for control points is essential to avoid misalignment and confusion.
What information should I include when contacting Support for a processing issue?
Include the processing task details file, job link, dataset IDs, and a brief description of the actions you have taken.