annotation export failure "keypoints array length does not match num_keypoints"

Not specified by the original author.

TL;DR

Fix this in the annotation platform by acting on the exact message first: reproduce the failure on the smallest single item first, note the exact inputs that trigger it, and change only the input or setting the error names. 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.

keypoints array length does not match num_keypoints

Use this when

• The operation in the annotation platform fails with this exact message: keypoints array length does not match num_keypoints.
• 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 annotation platform, 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: reproduce the failure on the smallest single item first, note the exact inputs that trigger it, and change only the input or setting the error names. Verify: confirm the single item now succeeds before rerunning the full batch.
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. Compare the result counts, decisions or alerts against the source in the annotation platform so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in the annotation platform 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.
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

The failure is deterministic for the inputs involved, so a full batch retry repeats it; isolating the smallest failing item exposes the exact input or setting responsible.

Variant phrasings

keypoints array length does not match num_keypoints

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: annotation export failure "keypoints array length does not match num_k

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

the annotation platform 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 annotation platform 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_pFqWqtCFhYt7JpOYtMAaZA

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

Thread query: annotation export failure "keypoints array length does not match num_keypoints"

TL;DR: Fix this in the annotation platform by acting on the exact message first: reproduce the failure on the smallest single item first, note the exact inputs that trigger it, and change only the input or setting the error names. 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 annotation export by acting on the exact message first: check whether rotation was applied twice, once from the image orientation metadata and once during export, then export with rotation handled in exactly one place, baked in or stripped consistently. 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.

bounding boxes shift by a few pixels after image rotation in annotation export error

Use this when

• The operation in the annotation export fails with this exact message: bounding boxes shift by a few pixels after image rotation in annotation export 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 annotation export, 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: check whether rotation was applied twice, once from the image orientation metadata and once during export, then export with rotation handled in exactly one place, baked in or stripped consistently. Verify: exported boxes sit on the same pixels as in the labeling view for rotated and unrotated images alike.
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 annotation export 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 annotation export 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

Orientation metadata rotates the displayed image; applying it again at export shifts every box by the rotation offset.

Variant phrasings

bounding boxes shift by a few pixels after image rotation in annotation export 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: bounding boxes shift by a few pixels after image rotation in annotation export error

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

the annotation export 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 annotation export 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_3qmH510DmqzNElUWHvsKaA

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

Thread query: bounding boxes shift by a few pixels after image rotation in annotation export error

TL;DR: Fix this in the annotation export by acting on the exact message first: check whether rotation was applied twice, once from the image orientation metadata and once during export, then export with rotation handled in exactly one place, baked in or stripped consistently. 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 CVAT by acting on the exact message first: export a single job first to isolate the failure, check the server log window for that job, repair or remove the one annotation the exporter stops on (usually a track with a missing keyframe), then export the full dataset. 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.

Annotations export failed with status 500

Use this when

• The operation in CVAT fails with this exact message: Annotations export failed with status 500.
• 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 CVAT, 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: export a single job first to isolate the failure, check the server log window for that job, repair or remove the one annotation the exporter stops on (usually a track with a missing keyframe), then export the full dataset. Verify: one job exports cleanly and the full export then completes with the expected file count.
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 CVAT 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 CVAT 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

The exporter serializes every track in order; one corrupt track fails the whole archive on the server side even though the other jobs are fine.

Variant phrasings

Annotations export failed with status 500

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: CVAT export failed error "Annotations export failed with status 500" on dataset download

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

CVAT 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: CVAT 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/pstCpvL050R9yff55vcz96_w

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

Thread query: CVAT export failed error "Annotations export failed with status 500" on dataset download

TL;DR: Fix this in CVAT by acting on the exact message first: export a single job first to isolate the failure, check the server log window for that job, repair or remove the one annotation the exporter stops on (usually a track with a missing keyframe), then export the full dataset. 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.