Skip to content

Update faq.mdx #25884

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 21, 2025
+13 −2
Merged

Update faq.mdx #25884

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
15c050a
Update faq.mdx
kathayl Oct 16, 2025
2aaada7
Update faq.mdx
kathayl Oct 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions src/content/docs/browser-rendering/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,3 +88,14 @@ It may be because you increased the height and width of the viewport. To fix thi
This error indicates you have hit the daily browser-instance limit on the Workers Free plan. [Free-plan accounts are capped at free plan limit is 10 minutes of browser use a day](/browser-rendering/platform/limits/#workers-free) once you exceed those, further creation attempts return a 429 until the next UTC day.

To resolve: [Upgrade to a Workers Paid plan](/workers/platform/pricing/) which allows for more than 10 minutes of usage a day and has higher [limits](/browser-rendering/platform/limits/#workers-paid). If you recently upgraded but still see this error, try redeploying your Worker to ensure your usage is correctly associated with your new plan.

### Why am I getting a `422 Unprocessable Entity` error?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Why am I getting a `422 Unprocessable Entity` error?
### `422 Unprocessable Entity` error

You an ignore this for now if you want to save it for another time, but I thought it might be better to have all of these error-specific troubleshooting steps just have the name of the error as the header to avoid having a bunch of headers all phrased differently ("I see x error", "I'm getting x error", "what do I do?" "how do I fix" etc) and just keep it very clear and simple.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are two other headers in this doc that could also use this update.


A `422 Unprocessable Entity` error usually means that Browser Rendering wasn’t able to complete an action because of an issue with the site, not your request.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A `422 Unprocessable Entity` error usually means that Browser Rendering wasn’t able to complete an action because of an issue with the site, not your request.
Sometimes a `422 Unprocessable Entity` error is caused by the website you are crawling, and not by Browser Rendering or your request. For example, the website might have crashed, errored out, or consumed too much memory during rendering.```

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought the logic of this one could be a little clearer and more straightforward. Because you started off by saying that it's not the request (but the fault of the website they're crawling), but in that third bullet point, you're saying that it is a problem with the request.

I would recommend breaking it into the two scenarios (the website's fault vs. the request's fault) and then perhaps add a sentence under each that explains what they can do about it.


This can happen if:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This can happen if:
However, it can also be caused by your request exceeding the [timeout limits](/browser-rendering/reference/timeouts/) for page load, element load, or an action. In this case, try [increasing the timeout limits](/browser-rendering/reference/timeouts/#notes-and-recommendations).

I added the step they can take - is this right?

- The website consumes too much memory during rendering.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- The website consumes too much memory during rendering.

- The page itself crashed or returned an error before the action completed.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- The page itself crashed or returned an error before the action completed.

- The request exceeded one of the [timeout limits](/browser-rendering/reference/timeouts/) for page load, element load, or an action.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- The request exceeded one of the [timeout limits](/browser-rendering/reference/timeouts/) for page load, element load, or an action.


Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change

Most often, this error is caused by a timeout. You can review the different timers and their limits in the [REST API timeouts reference](/browser-rendering/reference/timeouts/)).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Most often, this error is caused by a timeout. You can review the different timers and their limits in the [REST API timeouts reference](/browser-rendering/reference/timeouts/)).