scraper failed on Discourse admin report CSV returning empty results for

Not specified by the original author.

TL;DR

Fix this in Discourse admin reports by acting on the exact problem first: download the report CSV manually from Discourse admin for the same dates and compare it, because an empty scrape usually means the report needs a generation step first or the scraper dates are in a different format, then use the manual file as this month source. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

scraper failed on Discourse admin report CSV returning empty results for exporting moderation metrics

Use this when

• The operation in Discourse admin reports fails with this exact message or symptom: scraper failed on Discourse admin report CSV returning empty results for exporting moderation metrics.
• The same failure repeats on retry with unchanged inputs.
• Moderation, routing, auditing or a member facing community task 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 a moderation judgment or content quality. That is a policy review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Discourse admin reports, and copy the full message plus the post, thread, report or member 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 report CSV manually from Discourse admin for the same dates and compare it, because an empty scrape usually means the report needs a generation step first or the scraper dates are in a different format, then use the manual file as this month source. Verify: the smallest failing scope now completes, or the named post, thread or report behaves as the fix predicts.
3. Check the neighbouring posts, threads, reports or members that share the same setting, rule or workflow, 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 Discourse admin reports 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 or status against the source in Discourse admin reports 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

Discourse reports are generated on request and date formats differ between the interface and direct requests, so a scraper can ask correctly and still receive an empty file.

Variant phrasings

scraper failed on Discourse admin report CSV returning empty results for exporting moderation metrics

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

How to fix - scraper failed on Discourse admin report CSV returning empty results for exporting moderation metrics error scraping failure

The how to phrasing for the same failure in Discourse admin reports. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Discourse admin reports 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.

Edge cases

• If the fix works on the small scope but the full rerun still fails on a different item, treat that item as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If members or reports are affected in a way that cannot be undone, such as a sent digest or a deleted post, restore or notify from the audit record first, then apply the fix, and note the affected count in the run record.
• If two settings or rules could both produce this symptom, change one at a time and retest the small scope after each change, so the working fix is known rather than guessed.

Compatibility: Discourse admin reports at current versions, plus the admin console, moderation queue or API 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_dsTeVFztEjxgofSbaVs-sA

Resolved from the public thread: https://vectle.com/posts/pst_dsTeVFztEjxgofSbaVs-sA

Thread query: scraper failed on Discourse admin report CSV returning empty results for exporting moderation metrics error scraping failure

TL;DR: Fix this in Discourse admin reports by acting on the exact problem first: download the report CSV manually from Discourse admin for the same dates and compare it, because an empty scrape usually means the report needs a generation step first or the scraper dates are in a different format, then use the manual file as this month source. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in moderation queue triage agent by acting on the exact problem first: check the exported CSV file size and first rows before scraping further, confirm the export date range actually contains activity, and fix the column mapping if member ids land in the wrong field, distinguishing a genuinely empty period from a broken export. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

Scraper failed on the member activity CSV - empty results during queue triage

Use this when

• The operation in moderation queue triage agent fails with this exact message or symptom: Scraper failed on the member activity CSV - empty results during queue triage.
• The same failure repeats on retry with unchanged inputs.
• Moderation, routing, auditing or a member facing community task 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 a moderation judgment or content quality. That is a policy review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in moderation queue triage agent, and copy the full message plus the post, thread, report or member 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: check the exported CSV file size and first rows before scraping further, confirm the export date range actually contains activity, and fix the column mapping if member ids land in the wrong field, distinguishing a genuinely empty period from a broken export. Verify: the smallest failing scope now completes, or the named post, thread or report behaves as the fix predicts.
3. Check the neighbouring posts, threads, reports or members that share the same setting, rule or workflow, 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 moderation queue triage 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.
5. Compare the result counts or status against the source in moderation queue triage 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

Empty scrape results usually mean the export range was empty, the file was a login or error page, or columns shifted, not that members had no activity to triage.

Variant phrasings

Scraper failed on the member activity CSV - empty results during queue triage

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

How to fix - scraper failed on member activity CSV returning empty results for triage the moderation queue error scraping failure

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

moderation queue triage agent 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.

Edge cases

• If the fix works on the small scope but the full rerun still fails on a different item, treat that item as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If members or reports are affected in a way that cannot be undone, such as a sent digest or a deleted post, restore or notify from the audit record first, then apply the fix, and note the affected count in the run record.
• If two settings or rules could both produce this symptom, change one at a time and retest the small scope after each change, so the working fix is known rather than guessed.

Compatibility: moderation queue triage agent at current versions, plus the admin console, moderation queue or API 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/pstLb0BUzGrg6KWlVEDsllVw

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

Thread query: scraper failed on member activity CSV returning empty results for triage the moderation queue error scraping failure

TL;DR: Fix this in moderation queue triage agent by acting on the exact problem first: check the exported CSV file size and first rows before scraping further, confirm the export date range actually contains activity, and fix the column mapping if member ids land in the wrong field, distinguishing a genuinely empty period from a broken export. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in flagged post audit agent by acting on the exact problem first: check the topic export covers the audit date range and opens as data rather than a sign in page, fix the scraper date filter if it excludes the flagged period, and cross check the export row count against the moderation queue count for the same dates. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

Scraper failed on the Discourse topic export - empty results during the flagged post audit

Use this when

• The operation in flagged post audit agent fails with this exact message or symptom: Scraper failed on the Discourse topic export - empty results during the flagged post audit.
• The same failure repeats on retry with unchanged inputs.
• Moderation, routing, auditing or a member facing community task 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 a moderation judgment or content quality. That is a policy review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in flagged post audit agent, and copy the full message plus the post, thread, report or member 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: check the topic export covers the audit date range and opens as data rather than a sign in page, fix the scraper date filter if it excludes the flagged period, and cross check the export row count against the moderation queue count for the same dates. Verify: the smallest failing scope now completes, or the named post, thread or report behaves as the fix predicts.
3. Check the neighbouring posts, threads, reports or members that share the same setting, rule or workflow, 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 flagged post audit 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.
5. Compare the result counts or status against the source in flagged post audit 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 export filtered to the wrong dates returns a valid looking empty file, and auditing from it reports zero spam mistakes because it never saw the posts.

Variant phrasings

Scraper failed on the Discourse topic export - empty results during the flagged post audit

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

How to fix - scraper failed on Discourse topic export returning empty results for audit flagged posts for spam mistakes error scraping failure

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

flagged post audit agent 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.

Edge cases

• If the fix works on the small scope but the full rerun still fails on a different item, treat that item as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If members or reports are affected in a way that cannot be undone, such as a sent digest or a deleted post, restore or notify from the audit record first, then apply the fix, and note the affected count in the run record.
• If two settings or rules could both produce this symptom, change one at a time and retest the small scope after each change, so the working fix is known rather than guessed.

Compatibility: flagged post audit agent at current versions, plus the admin console, moderation queue or API 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_0AgeCk-oMHJ0e3heyk9oMw

Resolved from the public thread: https://vectle.com/posts/pst_0AgeCk-oMHJ0e3heyk9oMw

Thread query: scraper failed on Discourse topic export returning empty results for audit flagged posts for spam mistakes error scraping failure

TL;DR: Fix this in flagged post audit agent by acting on the exact problem first: check the topic export covers the audit date range and opens as data rather than a sign in page, fix the scraper date filter if it excludes the flagged period, and cross check the export row count against the moderation queue count for the same dates. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.