agent hallucinating NPS score not in source data for route a detract

Not specified by the original author.

TL;DR

Fix this in detractor routing agent by acting on the exact problem first: require the agent to quote the score from the response record it read, validate the quoted score against the stored response before notifying, and reject any routing where the score cannot be traced to a source record. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.

agent hallucinating NPS score not in source records for detractor routing

Use this when

• The operation in detractor routing agent fails with this exact problem or symptom: agent hallucinating NPS score not in source records for detractor routing.
• The same failure repeats on retry with unchanged inputs.
• NPS follow-up, routing or reporting is blocked until this item completes.

Not for this skill when

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

Steps

1. Reproduce the failure with the smallest scope that still shows it in detractor routing agent, and copy the full problem plus the response, contact or job involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: require the agent to quote the score from the response record it read, validate the quoted score against the stored response before notifying, and reject any routing where the score cannot be traced to a source record. Verify: the smallest failing scope now completes, or the named response, record or job behaves as the fix predicts.
3. Check the neighbouring responses, records or jobs that share the same config, segment 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 detractor routing agent 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.
5. Compare the result counts or status against the source in detractor routing agent 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 problem, the fix applied and the evidence of success.

Why it happens

When the agent summarises from memory instead of re reading the response, it can invent a plausible score, and only a source check before notification catches it.

Variant phrasings

agent hallucinating NPS score not in source records for detractor routing

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

How to fix - agent hallucinating NPS score not in source data for route a detractor response to the account owner error hallucination failure

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

detractor routing agent troubleshooting for this failure

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

Compatibility: detractor routing 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.

Edge cases: if the fix works on the small scope but the full rerun still fails on a different record, treat that record as a second instance of the same class, apply the same fix per record, and keep the verified records separate from the still failing ones.

Provenance

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

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

Thread query: agent hallucinating NPS score not in source data for route a detractor response to the account owner error hallucination failure

TL;DR: Fix this in detractor routing agent by acting on the exact problem first: require the agent to quote the score from the response record it read, validate the quoted score against the stored response before notifying, and reject any routing where the score cannot be traced to a source record. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in detractor alert routing agent by acting on the exact problem first: require the routed owner to exist in the account owner directory the agent read, validate the owner against that directory before sending the alert, and route to a named fallback owner with a warning when no valid owner is found instead of using an invented name. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.

agent hallucinating alert owner not in source data for routing detractor alerts error hallucination failure

Use this when

• The operation in detractor alert routing agent fails with this exact problem or symptom: agent hallucinating alert owner not in source data for routing detractor alerts error hallucination failure.
• The same failure repeats on retry with unchanged inputs.
• NPS follow-up, routing or reporting is blocked until this item completes.

Not for this skill when

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

Steps

1. Reproduce the failure with the smallest scope that still shows it in detractor alert routing agent, and copy the full problem plus the response, contact or job involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: require the routed owner to exist in the account owner directory the agent read, validate the owner against that directory before sending the alert, and route to a named fallback owner with a warning when no valid owner is found instead of using an invented name. Verify: the smallest failing scope now completes, or the named response, record or job behaves as the fix predicts.
3. Check the neighbouring responses, records or jobs that share the same config, segment 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 detractor alert routing agent 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.
5. Compare the result counts or status against the source in detractor alert routing agent 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 problem, the fix applied and the evidence of success.

Why it happens

The agent supplied a plausible owner name from context instead of the directory, and an alert sent to an invented owner reaches nobody while looking successfully routed.

Variant phrasings

agent hallucinating alert owner not in source data for routing detractor alerts error hallucination failure

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

How to fix - agent hallucinating alert owner not in source data for routing detractor alerts error hallucination failure

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

detractor alert routing agent troubleshooting for this failure

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

Compatibility: detractor alert routing 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.

Edge cases: if the fix works on the small scope but the full rerun still fails on a different record, treat that record as a second instance of the same class, apply the same fix per record, and keep the verified records separate from the still failing ones.

Provenance

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

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

Thread query: agent hallucinating alert owner not in source data for routing detractor alerts error hallucination failure

TL;DR: Fix this in detractor alert routing agent by acting on the exact problem first: require the routed owner to exist in the account owner directory the agent read, validate the owner against that directory before sending the alert, and route to a named fallback owner with a warning when no valid owner is found instead of using an invented name. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in detractor routing agent by acting on the exact problem first: add a visited check keyed on response identifier so the same response cannot be processed twice, cap routing attempts per response, and break the loop by marking this response routed once the owner notification is confirmed sent. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.

agent stuck loop - repeating the same NPS score while routing a detractor response

Use this when

• The operation in detractor routing agent fails with this exact problem or symptom: agent stuck loop - repeating the same NPS score while routing a detractor response.
• The same failure repeats on retry with unchanged inputs.
• NPS follow-up, routing or reporting is blocked until this item completes.

Not for this skill when

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

Steps

1. Reproduce the failure with the smallest scope that still shows it in detractor routing agent, and copy the full problem plus the response, contact or job involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: add a visited check keyed on response identifier so the same response cannot be processed twice, cap routing attempts per response, and break the loop by marking this response routed once the owner notification is confirmed sent. Verify: the smallest failing scope now completes, or the named response, record or job behaves as the fix predicts.
3. Check the neighbouring responses, records or jobs that share the same config, segment 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 detractor routing agent 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.
5. Compare the result counts or status against the source in detractor routing agent 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 problem, the fix applied and the evidence of success.

Why it happens

Without a processed marker the agent re reads the same unrouted response each cycle, repeats the same score handling, and never advances to the next response.

Variant phrasings

agent stuck loop - repeating the same NPS score while routing a detractor response

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

How to fix - agent stuck loop detected repeating the same NPS score while trying to route a detractor response to the account owner error failure

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

detractor routing agent troubleshooting for this failure

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

Compatibility: detractor routing 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.

Edge cases: if the fix works on the small scope but the full rerun still fails on a different record, treat that record as a second instance of the same class, apply the same fix per record, and keep the verified records separate from the still failing ones.

Provenance

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

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

Thread query: agent stuck loop detected repeating the same NPS score while trying to route a detractor response to the account owner error failure

TL;DR: Fix this in detractor routing agent by acting on the exact problem first: add a visited check keyed on response identifier so the same response cannot be processed twice, cap routing attempts per response, and break the loop by marking this response routed once the owner notification is confirmed sent. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.