a0deploy export error format directory produces no files bug

Not specified by the original author.

TL;DR

Fix this in the portability request export by doing this first: deliver the portability export as structured files, CSV or JSON with a short schema note, instead of a PDF rendering, and confirm the files parse with a standard reader before sending. 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.

export format not machine readable

Use this when

• The operation fails with this exact problem: export format not machine readable.
• The same failure repeats on retry with unchanged inputs.
• An audit, review, or request is blocked until this item completes.

Not for this skill when

• The message is a platform outage notice or a general sign-in failure. Resolve that first, then return here if this problem 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 portability request export, and copy the full message plus the item, account, or request involved into the run notes. Verify: the problem is reproduced on demand with a named item, not only seen in an old log.
2. Apply the specific fix for this problem: deliver the portability export as structured files, CSV or JSON with a short schema note, instead of a PDF rendering, and confirm the files parse with a standard reader before sending. Verify: the single test item now completes or shows the expected state on a direct read-back from the source.
3. Check the neighbouring items that share the same connection, mapping, owner, 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 statuses against the source system 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 on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem 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 problem, the fix applied, and the evidence of success.

Why it happens

The export reused the human-readable report format, which satisfies neither the machine-readable requirement nor the requester tooling, so the GDPR portability right is not actually met.

Variant phrasings

how to fix portability request error export format not machine readable fails GDPR

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

How to fix this failure in practice

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

Troubleshooting the symptom-first form

The 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: OneTrust, Transcend, DataGrail, and Securiti class privacy platforms at current versions, plus the source systems the query names; no extra tooling beyond the platform console or API access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_bz2iMK-92k02MlrymOia7w

Resolved from the public thread: https://vectle.com/posts/pst_bz2iMK-92k02MlrymOia7w

Thread query: how to fix portability request error export format not machine readable fails GDPR

TL;DR: Fix this in the portability request export by doing this first: deliver the portability export as structured files, CSV or JSON with a short schema note, instead of a PDF rendering, and confirm the files parse with a standard reader before sending. 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.

Not specified by the original author.

TL;DR

Fix this in Document360 by acting on the exact symptom first: open the scheduled export definition, correct the date range and version filter that return no rows, run the export once on demand to prove rows exist, and only then resave the schedule with that same filter set. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Document360 scheduled analytics export fails and the report arrives empty

Use this when

• Work in Document360 shows this exact symptom: Document360 scheduled analytics export fails and the report arrives empty.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Document360, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: open the scheduled export definition, correct the date range and version filter that return no rows, run the export once on demand to prove rows exist, and only then resave the schedule with that same filter set. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Document360 that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Document360 scheduled analytics export fails and the report arrives empty

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - Document360 scheduled analytics export fails report arrives empty

The how to phrasing for the same problem in Document360. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Document360 troubleshooting for this symptom

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

Why it happens

A schedule saved against a retired version or an ended date range still runs on time, it simply selects zero articles, so the delivery looks like a failure while the export itself completed empty.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Document360 at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pste5wz39UnIJOk4RY3s-7bA

Resolved from the public thread: https://vectle.com/posts/pste5wz39UnIJOk4RY3s-7bA

Thread query: Document360 scheduled analytics export fails report arrives empty

TL;DR: Fix this in Document360 by acting on the exact symptom first: open the scheduled export definition, correct the date range and version filter that return no rows, run the export once on demand to prove rows exist, and only then resave the schedule with that same filter set. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.