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.
Download processing task details: In IVION Processing, open the job menu (three dots) and choose Download processing 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 does a red status indicate in an IVION Processing job?
A red status indicates that processing has aborted due to incomplete or corrupt data or a software error, and no units are deducted.
What should I do if my processing job status is yellow?
If the status is yellow, inspect the control points and quality map, correct any issues, and re-run the processing.
How can I gather evidence before contacting Support?
You should collect the processing task details file, job link, site name, dataset IDs, and a short description of what actions you have already taken.
What are common causes of a BagIOException / BZ_IO_ERROR?
This error typically indicates corrupted bag files during copy or upload, often due to issues with local storage or network stability.
When should I escalate an issue to Support?
You should contact Support if a clean re-upload fails, if the yellow status persists after fixing control points, or if logs show unclear or internal errors.
Why did my job show Finished (yellow) instead of Failure (red)?
Yellow indicates the pipeline completed but control point residuals were high or alignment was poor. Correct control points and re-run; note that both runs consume units.
Will I be charged for a failed (red) processing job?
No. Units Consumed remain empty and no units are deducted when status is Failure (red).