agent failed to reconcile survey respondent identities across CRM and survey

Not specified by the original author.

TL;DR

Fix this in identity reconciliation agent by acting on the exact problem first: reconcile identities in small batches keyed on the strongest identifier first, save each confirmed match immediately, treat name only pairs as review candidates instead of matches, and resume from the first unreconciled respondent so a timeout loses only the current batch. 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 failed to reconcile survey respondent identities across CRM and survey platform error failure timeout

Use this when

• The operation in identity reconciliation agent fails with this exact problem or symptom: agent failed to reconcile survey respondent identities across CRM and survey platform error failure timeout.
• 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 identity reconciliation 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: reconcile identities in small batches keyed on the strongest identifier first, save each confirmed match immediately, treat name only pairs as review candidates instead of matches, and resume from the first unreconciled respondent so a timeout loses only the current batch. 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 identity reconciliation 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 identity reconciliation 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

A full population match in one run grows with both contact lists, and unsaved progress means the timeout discards matches the agent had already confirmed.

Variant phrasings

agent failed to reconcile survey respondent identities across CRM and survey platform error failure timeout

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 failed to reconcile survey respondent identities across CRM and survey platform error failure timeout

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

identity reconciliation 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: identity reconciliation 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_2tIkT8noVNUvVaBkwO0Iow

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

Thread query: agent failed to reconcile survey respondent identities across CRM and survey platform error failure timeout

TL;DR: Fix this in identity reconciliation agent by acting on the exact problem first: reconcile identities in small batches keyed on the strongest identifier first, save each confirmed match immediately, treat name only pairs as review candidates instead of matches, and resume from the first unreconciled respondent so a timeout loses only the current batch. 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 identity reconciliation agent scraper by acting on the exact problem first: download the CRM contact export as a file instead of scraping the rendered list, confirm its row count before reconciling, and treat an empty download as an export fault to retry rather than proof there are no contacts. 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.

scraper failed on CRM contact export returning empty results for reconciling survey identities error scraping failure

Use this when

• The operation in identity reconciliation agent scraper fails with this exact problem or symptom: scraper failed on CRM contact export returning empty results for reconciling survey identities error scraping 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 identity reconciliation agent scraper, 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: download the CRM contact export as a file instead of scraping the rendered list, confirm its row count before reconciling, and treat an empty download as an export fault to retry rather than proof there are no contacts. 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 identity reconciliation agent scraper 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 identity reconciliation agent scraper 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

A rendered contact list that loads asynchronously returns empty to a fast scraper, and reconciling against an empty set falsely reports every respondent as unmatched.

Variant phrasings

scraper failed on CRM contact export returning empty results for reconciling survey identities error scraping 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 - scraper failed on CRM contact export returning empty results for reconciling survey identities error scraping failure

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

identity reconciliation agent scraper 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: identity reconciliation agent scraper 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_Tc6rhaF6OJtPuw6yS1-HXg

Resolved from the public thread: https://vectle.com/posts/pst_Tc6rhaF6OJtPuw6yS1-HXg

Thread query: scraper failed on CRM contact export returning empty results for reconciling survey identities error scraping failure

TL;DR: Fix this in identity reconciliation agent scraper by acting on the exact problem first: download the CRM contact export as a file instead of scraping the rendered list, confirm its row count before reconciling, and treat an empty download as an export fault to retry rather than proof there are no contacts. 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 identity reconciliation agent by acting on the exact problem first: resolve identities against a local copy of the CRM contacts downloaded in bulk, spend API calls only on the small set of ambiguous matches, and record resolved respondents locally so a resumed run never re spends quota on them. 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.

API rate limit hit mid-workflow when agent tried to reconcile survey respondent identities error failed quota

Use this when

• The operation in identity reconciliation agent fails with this exact problem or symptom: API rate limit hit mid-workflow when agent tried to reconcile survey respondent identities error failed quota.
• 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 identity reconciliation 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: resolve identities against a local copy of the CRM contacts downloaded in bulk, spend API calls only on the small set of ambiguous matches, and record resolved respondents locally so a resumed run never re spends quota on them. 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 identity reconciliation 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 identity reconciliation 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

Live lookups per respondent exhaust quota on the easy matches that a local index would resolve for free, leaving no quota for the ambiguous cases that actually need the API.

Variant phrasings

API rate limit hit mid-workflow when agent tried to reconcile survey respondent identities error failed quota

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 - API rate limit hit mid-workflow when agent tried to reconcile survey respondent identities error failed quota

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

identity reconciliation 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: identity reconciliation 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_QIMgJB77m7H-9EQ5H1ETcw

Resolved from the public thread: https://vectle.com/posts/pst_QIMgJB77m7H-9EQ5H1ETcw

Thread query: API rate limit hit mid-workflow when agent tried to reconcile survey respondent identities error failed quota

TL;DR: Fix this in identity reconciliation agent by acting on the exact problem first: resolve identities against a local copy of the CRM contacts downloaded in bulk, spend API calls only on the small set of ambiguous matches, and record resolved respondents locally so a resumed run never re spends quota on them. 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.