scraper failed on Salesforce contact list returning empty results for generate

Not specified by the original author.

TL;DR

Fix this in follow-up task agent by acting on the exact problem first: verify whether the contact list is empty at the source or the scrape missed rendered rows, fall back to a Salesforce report export for owner details, and never emit an ownerless task list from an empty scrape. 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 Salesforce contact list - empty results for follow-up task generation

Use this when

• The operation in follow-up task agent fails with this exact problem or symptom: scraper failed on Salesforce contact list - empty results for follow-up task generation.
• 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 follow-up task 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: verify whether the contact list is empty at the source or the scrape missed rendered rows, fall back to a Salesforce report export for owner details, and never emit an ownerless task list from an empty scrape. 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 follow-up task 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 follow-up task 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

An empty scrape silently produces tasks with no owners, and distinguishing a source problem from a rendering problem decides whether to fix the scrape or the list itself.

Variant phrasings

scraper failed on Salesforce contact list - empty results for follow-up task generation

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 Salesforce contact list returning empty results for generate an NPS follow-up task list error scraping failure

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

follow-up task 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: follow-up task 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_7ArX9Tfm4ltjK3pAaxdzPA

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

Thread query: scraper failed on Salesforce contact list returning empty results for generate an NPS follow-up task list error scraping failure

TL;DR: Fix this in follow-up task agent by acting on the exact problem first: verify whether the contact list is empty at the source or the scrape missed rendered rows, fall back to a Salesforce report export for owner details, and never emit an ownerless task list from an empty scrape. 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 Broken redirect crawl agent by acting on the exact symptom first: fall back to the sitemap index and the article export when page scraping returns empty, confirm the address count against the published article count, and never run a redirect audit on an empty address list. 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.

Scraper failed on the help center sitemap and returned empty results for crawling broken redirects

Use this when

• Work in Broken redirect crawl agent shows this exact symptom: Scraper failed on the help center sitemap and returned empty results for crawling broken redirects.
• 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 Broken redirect crawl agent, 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: fall back to the sitemap index and the article export when page scraping returns empty, confirm the address count against the published article count, and never run a redirect audit on an empty address list. 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 Broken redirect crawl agent 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

Scraper failed on the help center sitemap and returned empty results for crawling broken redirects

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 - scraper failed on help center sitemap returning empty results for crawling broken redirects error scraping failure

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

Broken redirect crawl agent 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

The sitemap is generated as structured data that a plain page scrape reads as empty, so empty output described the scraping method, not a missing sitemap.

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: Broken redirect crawl agent 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/pst_2zL02tXrA0ux8tGUvMlbAw

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

Thread query: scraper failed on help center sitemap returning empty results for crawling broken redirects error scraping failure

TL;DR: Fix this in Broken redirect crawl agent by acting on the exact symptom first: fall back to the sitemap index and the article export when page scraping returns empty, confirm the address count against the published article count, and never run a redirect audit on an empty address list. 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.

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.