Prodigy stream error "No tasks available: dataset is empty" when starting ner session

Not specified by the original author.

TL;DR

Fix this in Prodigy by acting on the exact message first: check the source path the recipe loads, confirm the input file actually has records and the loader matches its format, then restart the session so the stream is rebuilt from the corrected source. 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.

No tasks available: dataset is empty

Use this when

• The operation in Prodigy fails with this exact message: No tasks available: dataset is empty.
• 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 Prodigy, 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: check the source path the recipe loads, confirm the input file actually has records and the loader matches its format, then restart the session so the stream is rebuilt from the corrected source. Verify: the session serves a first task and the stream counter shows the expected total.
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 Prodigy 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 Prodigy 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

The stream is built from the source at session start; an empty or misread source produces an empty stream even though the dataset name looks right.

Variant phrasings

No tasks available: dataset is empty

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: Prodigy stream error "No tasks available: dataset is empty" when starting ner session

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

Prodigy 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: Prodigy 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_ce0u5ELrcf451h6mQ1JDVA

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

Thread query: Prodigy stream error "No tasks available: dataset is empty" when starting ner session

TL;DR: Fix this in Prodigy by acting on the exact message first: check the source path the recipe loads, confirm the input file actually has records and the loader matches its format, then restart the session so the stream is rebuilt from the corrected source. 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 Mostly AI console by acting on the exact message first: check whether the export is available through the Mostly AI API and use that instead of the console, if the console must be used restore the saved signed in session, wait for the export button state by name rather than a fixed sleep, and capture a screenshot and page text at the failure point to separate a login wall from a disabled export. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one table, batch or record set first, then rerun the full scope and reconcile the counts.

browser automation failed on synthetic dataset export - automation blocked

Use this when

• The operation in Mostly AI console fails with this exact message or symptom: browser automation failed on synthetic dataset export - automation blocked.
• The same failure repeats on retry with unchanged inputs.
• Generation, validation or export 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 error 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 Mostly AI console, and copy the full message plus the table, column or job involved into the run notes. Verify: the error is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this error: check whether the export is available through the Mostly AI API and use that instead of the console, if the console must be used restore the saved signed in session, wait for the export button state by name rather than a fixed sleep, and capture a screenshot and page text at the failure point to separate a login wall from a disabled export. Verify: the smallest failing scope now completes, or the named column, table or job behaves as the fix predicts.
3. Check the neighbouring tables, columns or jobs that share the same config, schema 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 Mostly AI console 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, distributions or status against the source in Mostly AI console 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

Console exports sit behind signed in, client side rendered pages, and automation that arrives with a stale session or clicks before rendering finishes is blocked or times out while the dataset itself is ready.

Variant phrasings

browser automation failed on synthetic dataset export - automation blocked

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

How to fix - agent browser automation failed on Mostly AI console synthetic dataset export blocked

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

Mostly AI console 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: Mostly AI console at current versions, plus the platform API or console 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/pstLGYKjM4k96T84DMhGsPNg

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

Thread query: agent browser automation failed on Mostly AI console synthetic dataset export blocked

TL;DR: Fix this in Mostly AI console by acting on the exact message first: check whether the export is available through the Mostly AI API and use that instead of the console, if the console must be used restore the saved signed in session, wait for the export button state by name rather than a fixed sleep, and capture a screenshot and page text at the failure point to separate a login wall from a disabled export. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one table, batch or record set first, then rerun the full scope and reconcile the co

Not specified by the original author.

TL;DR

Fix this in the clause agent workflow by acting on the exact problem first: replace the empty result handling for the task to compare a negotiated clause against the playbook position so the agent falls back to the clause library API when scraping returns nothing, log the empty response for review, and confirm the workflow completes with API results. Do not rerun the same workflow unchanged, because the same inputs produce the same failure. Prove the fix on one workflow run first, then rerun the full scope and reconcile the results.

scraper failed returning empty results when agent tried to compare a negotiated clause against the playbook position error scraping failure

Use this when

• The agent workflow fails with this exact problem: scraper failed returning empty results when agent tried to compare a negotiated clause against the playbook position error scraping failure.
• The same failure repeats on retry with unchanged inputs.
• A clause search, drafting, review or reporting task run by the agent is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor or the clause bank provider. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a clause wording or negotiation position. That is a legal owner decision, not this failure.

Steps

1. Reproduce the failure on one named run of the task to compare a negotiated clause against the playbook position and record the full problem text plus the contract or clause set involved. Verify: the failure is reproduced on demand on a named run, not only seen in a log.
2. Apply the specific fix for this problem: replace the empty result handling for the task to compare a negotiated clause against the playbook position so the agent falls back to the clause library API when scraping returns nothing, log the empty response for review, and confirm the workflow completes with API results. Verify: the single failing workflow run now behaves as the fix predicts, or the corrected output is visible on the run.
3. Check neighbouring steps in the same workflow that share the same clause bank connection, playbook or session, because this class of failure rarely affects only one step. Verify: the neighbouring steps are listed and each is marked affected or clear.
4. Rerun the original task in the workflow on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the task completes and the original problem does not appear.
5. Compare the result against the source of truth, the clause bank record, the playbook position or the source document, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the workflow run log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

scraper failed returning empty results when agent tried to compare a negotiated clause against the playbook position error scraping failure

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

How to fix - scraper failed returning empty results when agent tried to compare a negotiated clause against the playbook position error scraping failure

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

The clause agent workflow troubleshooting for this failure

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

Why it happens

The scraper reads a rendered page or listing that changed shape or now loads its content after the scrape runs, so the run completes normally while collecting no clause content at all.

Edge cases

• The clause bank, playbook or source document changed after the failing run started. Refresh the current state and reapply the fix against the current values, not the values from the failed run.
• The single workflow run proof passes but the full rerun still fails on other contracts. Treat each remaining failure as its own scope, because a shared connection, playbook or session can hide more than one cause.
• The source systems disagree on the correct value. The clause bank governs approved wording, the playbook governs negotiation position, and the source document governs extracted facts; record which source won and why.

Compatibility: Clause library and agent workflow tooling at current versions, plus the clause bank, playbook or document source the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ZyfCGnbeM-EN5W6bh4UXxg

Resolved from the public thread: https://vectle.com/posts/pst_ZyfCGnbeM-EN5W6bh4UXxg

Thread query: scraper failed returning empty results when agent tried to compare a negotiated clause against the playbook position error scraping failure

TL;DR: Fix this in the clause agent workflow by acting on the exact problem first: replace the empty result handling for the task to compare a negotiated clause against the playbook position so the agent falls back to the clause library API when scraping returns nothing, log the empty response for review, and confirm the workflow completes with API results. Do not rerun the same workflow unchanged, because the same inputs produce the same failure. Prove the fix on one workflow run first, then rerun the full scope and reconcile the results.