Kili export failed error "Label asset not found for project" during download

Not specified by the original author.

TL;DR

Fix this in Kili by acting on the exact message first: list the assets in the project and compare their ids with the ids the labels reference, restore or re-upload the missing asset under the same external id, then restart the export. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Label asset not found for project

Use this when

• The operation in Kili fails with this exact message: Label asset not found for project.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Kili, and copy the full message plus the item, user or metric involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: list the assets in the project and compare their ids with the ids the labels reference, restore or re-upload the missing asset under the same external id, then restart the export. Verify: the export resolves every referenced asset and produces output for all of them.
3. Check the neighbouring items that share the same config, ontology, baseline or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Kili on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts, decisions or alerts against the source in Kili so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

Labels point at assets by id; deleting or re-uploading an asset under a new id orphans the labels that reference it.

Variant phrasings

Label asset not found for project

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: Kili export failed error "Label asset not found for project" during download

The how-to phrasing for the same failure in Kili. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Kili troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Kili at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_AY4qncf-w9eGj4hsSHw8wg

Resolved from the public thread: https://vectle.com/posts/pst_AY4qncf-w9eGj4hsSHw8wg

Thread query: Kili export failed error "Label asset not found for project" during download

TL;DR: Fix this in Kili by acting on the exact message first: list the assets in the project and compare their ids with the ids the labels reference, restore or re-upload the missing asset under the same external id, then restart the export. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in the Kili label JSON by acting on the exact message first: walk the classifications array recursively, read answers at each level before flattening, and keep the job name with each flattened answer so nested answers stay attributable. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

parser failed on Kili label JSON with nested classifications array error

Use this when

• The operation in the Kili label JSON fails with this exact message: parser failed on Kili label JSON with nested classifications array error.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the Kili label JSON, and copy the full message plus the item, user or metric involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: walk the classifications array recursively, read answers at each level before flattening, and keep the job name with each flattened answer so nested answers stay attributable. Verify: every classification in the source appears once in the parsed output with its job name.
3. Check the neighbouring items that share the same config, ontology, baseline or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in the Kili label JSON on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts, decisions or alerts against the source in the Kili label JSON so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

Kili nests classification answers inside parent answers; a flat reader sees only the top level and misses or mangles the nested jobs.

Variant phrasings

parser failed on Kili label JSON with nested classifications array error

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: parser failed on Kili label JSON with nested classifications array error

The how-to phrasing for the same failure in the Kili label JSON. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the Kili label JSON troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the Kili label JSON at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_AGVsxzeC5gqD2QXe8TBFxw

Resolved from the public thread: https://vectle.com/posts/pst_AGVsxzeC5gqD2QXe8TBFxw

Thread query: parser failed on Kili label JSON with nested classifications array error

TL;DR: Fix this in the Kili label JSON by acting on the exact message first: walk the classifications array recursively, read answers at each level before flattening, and keep the job name with each flattened answer so nested answers stay attributable. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in the two exports by acting on the exact message first: convert both exports to one common form such as COCO before comparing, normalize class names and coordinate conventions in that form, and compare only after the conversion checks pass. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

when agent tried to compare CVAT and Label Studio exports it failed with format mismatch error

Use this when

• The operation in the two exports fails with this exact message: when agent tried to compare CVAT and Label Studio exports it failed with format mismatch error.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the two exports, and copy the full message plus the item, user or metric involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: convert both exports to one common form such as COCO before comparing, normalize class names and coordinate conventions in that form, and compare only after the conversion checks pass. Verify: both converted files validate and the comparison reports real differences only.
3. Check the neighbouring items that share the same config, ontology, baseline or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in the two exports on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts, decisions or alerts against the source in the two exports so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

CVAT and Label Studio exports encode the same labels differently; comparing the raw files reports format differences as content differences.

Variant phrasings

when agent tried to compare CVAT and Label Studio exports it failed with format mismatch error

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: when agent tried to compare CVAT and Label Studio exports it failed with format mismatch error

The how-to phrasing for the same failure in the two exports. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the two exports troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the two exports at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstt-lNLq5H2lHAkpaP1Uwkw

Resolved from the public thread: https://vectle.com/posts/pstt-lNLq5H2lHAkpaP1Uwkw

Thread query: when agent tried to compare CVAT and Label Studio exports it failed with format mismatch error

TL;DR: Fix this in the two exports by acting on the exact message first: convert both exports to one common form such as COCO before comparing, normalize class names and coordinate conventions in that form, and compare only after the conversion checks pass. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.