agent hallucinating annotator IDs that do not exist caused routing failure

Not specified by the original author.

TL;DR

Fix this in the annotation platform by acting on the exact message first: constrain the agent to ids and values returned by the source API in this run, reject any label, reviewer or cause not in that returned set, and log the rejection. 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.

agent hallucinating annotator IDs that do not exist caused routing failure

Use this when

• The operation in the annotation platform fails with this exact message: agent hallucinating annotator IDs that do not exist caused routing failure.
• 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: constrain the agent to ids and values returned by the source API in this run, reject any label, reviewer or cause not in that returned set, and log the rejection. Verify: rerun the step and confirm every emitted id exists in the source response.
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

When the source call fails or returns little, a model fills the gap with plausible values; grounding output in the returned payload removes the gap it fills.

Variant phrasings

agent hallucinating annotator IDs that do not exist caused routing fai

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: agent hallucinating annotator IDs that do not exist caused routing fai

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_21N996hE4AyCSEqJtc8Axg

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

Thread query: agent hallucinating annotator IDs that do not exist caused routing failure

TL;DR: Fix this in the annotation platform by acting on the exact message first: constrain the agent to ids and values returned by the source API in this run, reject any label, reviewer or cause not in that returned set, and log the rejection. 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: add a stop condition: a visited set, a max attempts counter of 3, and a changed input requirement before any retry is allowed. 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.

agent loop detected: agent hallucinating reviewer assignments in a loop after routing failure

Use this when

• The operation in the annotation platform fails with this exact message: agent loop detected: agent hallucinating reviewer assignments in a loop after routing failure.
• 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: add a stop condition: a visited set, a max attempts counter of 3, and a changed input requirement before any retry is allowed. Verify: run the loop guard on the failing item and confirm it exits after the limit with a clear reason.
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

A retry with identical inputs produces the identical failure; without a counter or state change the agent cycles forever on the same item.

Variant phrasings

agent loop detected: agent hallucinating reviewer assignments in a loo

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: agent loop detected: agent hallucinating reviewer assignments in a loo

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_8QsrCBlnOlS0NWix-5Hcmg

Resolved from the public thread: https://vectle.com/posts/pst_8QsrCBlnOlS0NWix-5Hcmg

Thread query: agent loop detected: agent hallucinating reviewer assignments in a loop after routing failure

TL;DR: Fix this in the annotation platform by acting on the exact message first: add a stop condition: a visited set, a max attempts counter of 3, and a changed input requirement before any retry is allowed. 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 annotator report by acting on the exact message first: compute every statistic from the exported task data, show the query or count behind each number in the report, and drop any figure that cannot be traced to 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.

agent hallucinating annotator productivity stats not in dashboard caused report failure error

Use this when

• The operation in the annotator report fails with this exact message: agent hallucinating annotator productivity stats not in dashboard caused report failure 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 annotator report, 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: compute every statistic from the exported task data, show the query or count behind each number in the report, and drop any figure that cannot be traced to the export. Verify: each reported number reproduces from the export with the stated filter.
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 annotator report 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 annotator report 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

Stats recalled from memory or inferred from partial views invent numbers that no export supports, and the report fails review.

Variant phrasings

agent hallucinating annotator productivity stats not in dashboard caused report failure 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: agent hallucinating annotator productivity stats not in dashboard caused report failure error

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

the annotator report 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 annotator report 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/pst5eM3J09oVKJxs9PVlrVQg

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

Thread query: agent hallucinating annotator productivity stats not in dashboard caused report failure error

TL;DR: Fix this in the annotator report by acting on the exact message first: compute every statistic from the exported task data, show the query or count behind each number in the report, and drop any figure that cannot be traced to 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.