## TL;DR
Fix this in synthetic data portal by acting on the exact message first: stop driving the portal for status, check job state through the API or a saved status link where one exists, and when the portal must be used, wait on a named element state with session re authentication handled explicitly instead of fixed sleeps. 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.

```text
browser automation failed on synthetic data portal - timeout blocked
```

## Use this when
- The operation in synthetic data portal fails with this exact message or symptom: browser automation failed on synthetic data portal - timeout 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 synthetic data portal, 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: stop driving the portal for status, check job state through the API or a saved status link where one exists, and when the portal must be used, wait on a named element state with session re authentication handled explicitly instead of fixed sleeps. 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 synthetic data portal 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 synthetic data portal 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
Portal pages load job state asynchronously and expire sessions silently, so fixed sleep automation times out or reads a blocked page as a job failure.

## Variant phrasings

### browser automation failed on synthetic data portal - timeout 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 - browser automation failed on synthetic data portal error timeout blocked failure
The how-to phrasing for the same failure in synthetic data portal. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

### synthetic data portal 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: synthetic data portal 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_f_CNkHTqt9HXHMVyouldyg