a0deploy export error keyword mappings missing in output bug

Not specified by the original author.

TL;DR

Fix this in Enrichment agent by acting on the exact message first: only report surge topics that appear as rows in the provider export for that company, join intent claims to the export by company domain, and remove every topic claim with no matching export row. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Agent invented intent data, it claimed Bombora surge topics absent from the provider export

Use this when

• The operation in Enrichment agent fails with this exact message: Agent invented intent data, it claimed Bombora surge topics absent from the provider export.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. 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 Enrichment agent, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: only report surge topics that appear as rows in the provider export for that company, join intent claims to the export by company domain, and remove every topic claim with no matching export row. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in Enrichment agent 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 Enrichment agent 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 record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

Summarising intent from company context produces plausible topics, and without a row level check against the export those inventions read exactly like real signals.

Variant phrasings

Agent invented intent data, it claimed Bombora surge topics absent from the provider export

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

How to fix this failure in Enrichment agent

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 this failure in Enrichment agent

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: Enrichment agent at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

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

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

Thread query: agent hallucinated intent data claimed Bombora surge topics absent from provider export

TL;DR: Fix this in Enrichment agent by acting on the exact message first: only report surge topics that appear as rows in the provider export for that company, join intent claims to the export by company domain, and remove every topic claim with no matching export row. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in the annotation platform by acting on the exact message first: check the class distribution before the kappa math: with one class or near total prevalence kappa is undefined or misleading, so report percent agreement and prevalence alongside it. 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 export disagreement report it failed with missing column error

Use this when

• The operation in the annotation platform fails with this exact message: when agent tried to export disagreement report it failed with missing column 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 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: check the class distribution before the kappa math: with one class or near total prevalence kappa is undefined or misleading, so report percent agreement and prevalence alongside it. Verify: recompute on a sample with at least two classes present and confirm a finite score.
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 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.
5. 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.
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

Kappa corrects for chance agreement; when every item has the same label there is no variation to correct and the calculation divides by near zero.

Variant phrasings

when agent tried to export disagreement report it failed with missing

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 export disagreement report it failed with missing

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_USAGk8S-n2J3RJ6XS0YXGA

Resolved from the public thread: https://vectle.com/posts/pst_USAGk8S-n2J3RJ6XS0YXGA

Thread query: when agent tried to export disagreement report it failed with missing column error

TL;DR: Fix this in the annotation platform by acting on the exact message first: check the class distribution before the kappa math: with one class or near total prevalence kappa is undefined or misleading, so report percent agreement and prevalence alongside it. 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 platform by acting on the exact message first: check the class distribution before the kappa math: with one class or near total prevalence kappa is undefined or misleading, so report percent agreement and prevalence alongside it. 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 export disagreement report it failed with missing column error

Use this when

• The operation in the annotation platform fails with this exact message: when agent tried to export disagreement report it failed with missing column 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 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: check the class distribution before the kappa math: with one class or near total prevalence kappa is undefined or misleading, so report percent agreement and prevalence alongside it. Verify: recompute on a sample with at least two classes present and confirm a finite score.
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 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.
5. 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.
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

Kappa corrects for chance agreement; when every item has the same label there is no variation to correct and the calculation divides by near zero.

Variant phrasings

when agent tried to export disagreement report it failed with missing

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 export disagreement report it failed with missing

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/pstiXMs4vV4EPLx5rYr_jo9A

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

Thread query: when agent tried to export disagreement report it failed with missing column error

TL;DR: Fix this in the annotation platform by acting on the exact message first: check the class distribution before the kappa math: with one class or near total prevalence kappa is undefined or misleading, so report percent agreement and prevalence alongside it. 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.