Update faq.mdx #25884
Update faq.mdx #25884
Conversation
add new FAQ on 422s
kathayl
requested review from
a team,
ToriLindsay,
celso and
mchenco
as code owners
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
|
Preview URL: https://15c050a1.preview.developers.cloudflare.com Files with changes (up to 15)
|
|
|
||
| ### Why am I getting a `422 Unprocessable Entity` error? | ||
|
|
||
| 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. |
There was a problem hiding this comment.
| 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.``` |
There was a problem hiding this comment.
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.
|
|
||
| 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. | ||
|
|
||
| This can happen if: |
There was a problem hiding this comment.
| 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?
| 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. | ||
|
|
||
| This can happen if: | ||
| - The website consumes too much memory during rendering. |
There was a problem hiding this comment.
| - The website consumes too much memory during rendering. |
|
|
||
| This can happen if: | ||
| - The website consumes too much memory during rendering. | ||
| - The page itself crashed or returned an error before the action completed. |
There was a problem hiding this comment.
| - The page itself crashed or returned an error before the action completed. |
| This can happen if: | ||
| - The website consumes too much memory during rendering. | ||
| - 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. |
There was a problem hiding this comment.
| - The request exceeded one of the [timeout limits](/browser-rendering/reference/timeouts/) for page load, element load, or an action. |
| - The website consumes too much memory during rendering. | ||
| - 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. | ||
|
|
| - 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. | ||
|
|
||
| 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/)). |
There was a problem hiding this comment.
| 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/)). |
|
|
||
| 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? |
There was a problem hiding this comment.
| ### 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.
There was a problem hiding this comment.
There are two other headers in this doc that could also use this update.
6 participants
add new FAQ on 422s
Summary
Screenshots (optional)
Documentation checklist