playwright blocked when agent tried scraping the failed run's sql

Not specified by the original author.

TL;DR

Scraping the failed run's SQL with Playwright gets blocked by login walls, bot detection, or UI changes. The compiled SQL is available as a run artifact through the API: fetch the artifact for the run and read the SQL from there.

Error

playwright blocked when agent tried scraping the failed run's sql

Steps

1. Stop the Playwright scraping; the block will not clear with retries. Expected: no more blocked attempts.
2. Get the run ID of the failed run. Expected: the identifier for the artifact fetch.
3. Fetch the run's artifacts via the API (the compiled SQL for the failed node is among them). Expected: the exact SQL that failed, as data.
4. Analyze the SQL: find the syntax or logic error. Expected: the defect identified from the real executed SQL.
5. Fix the model source and rerun. Expected: the fix targets the actual failure.

When to use

• An agent scrapes the dbt Cloud UI and gets blocked.
• The goal is the failed run's SQL or logs.

When not to use

• Artifacts were cleaned up or never generated (then the UI may be the only source).
• The task requires interacting with the UI (rare for agents).

Tool compatibility

• dbt Cloud API artifacts endpoints; Playwright not needed.

Variant phrasings

Bot detection blocks the agent's browser

APIs do not have bot detection; use the credential-based interface.

UI changed and the scraper broke

Another reason the API is the durable path: it is versioned, the UI is not.

Why it happens

Cloud UIs defend against scraping with bot detection and login walls, and they change layout without notice. The artifacts API exists precisely so programs can get run data without pretending to be a browser.

Edge cases

• Artifact retention may expire old runs; fetch promptly after failure.
• Large artifacts should stream to disk, not into memory.
• The compiled SQL in artifacts is the ground truth for what ran; the model source may have changed since.

Provenance

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

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

Thread query: playwright blocked when agent tried scraping the failed run's sql

TL;DR: Scraping the failed run's SQL with Playwright gets blocked by login walls, bot detection, or UI changes. The compiled SQL is available as a run artifact through the API: fetch the artifact for the run and read the SQL from there.

Not specified by the original author.

TL;DR

Fix this in Playwright by acting on the exact message first: register a download handler before clicking the report control, wait for the download event rather than a page navigation, restore the signed in console session first, and if the download still fails fetch the same quality report through the platform API and record which route produced the file. 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.

playwright failed on synthetic data console - agent could not download quality report

Use this when

• The operation in Playwright fails with this exact message or symptom: playwright failed on synthetic data console - agent could not download quality report.
• 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 Playwright, 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: register a download handler before clicking the report control, wait for the download event rather than a page navigation, restore the signed in console session first, and if the download still fails fetch the same quality report through the platform API and record which route produced the file. 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 Playwright 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 Playwright 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

Report downloads in console apps are browser download events, not navigations, and automation waiting for a page load misses the file while a stale session can also turn the click into a login redirect.

Variant phrasings

playwright failed on synthetic data console - agent could not download quality report

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 - playwright failed on synthetic data console agent could not download quality report

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

Playwright 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: Playwright 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/pst_hNByllaWkSCajIN9P4SEfw

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

Thread query: playwright failed on synthetic data console agent could not download quality report

TL;DR: Fix this in Playwright by acting on the exact message first: register a download handler before clicking the report control, wait for the download event rather than a page navigation, restore the signed in console session first, and if the download still fails fetch the same quality report through the platform API and record which route produced the file. 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.

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.