Solutions by extraction failure message
If extraction fails, you can determine the cause based on what is shown in the screenshot and get guidance on appropriate solutions. Follow the steps below to resolve the issue.
✅ Step 1. Immediately after extraction fails, first check the items below.
1. Wait a short time and try extracting again.
It may have been a one-time issue due to temporary loading failure of the target site, server error, etc.
→ Try again after an interval of several minutes or more. If the same problem repeats after retrying, refer to the screen-type guide in Step 2 below.
2. Are you running many tasks simultaneously?
Running many tasks at once can cause errors due to processing bottlenecks.
→ If you are doing group extraction, try reducing the number of URLs per group.
→ If it is a single task (such as a scheduled job), it is recommended to stagger them to distribute the workload.
3. If failures repeat, check whether the error code or screenshot has changed
The error code or the screenshot shown when you retry may reveal a more specific cause than before.
→ If the code or on-screen message has changed, check the guide for that situation in Step 2.
✅ Step 2. Please select the screen type shown in the error screenshot

When extraction fails, a “screenshot” is generated instead of a result. Here, the error type and the screen the collector encountered when accessing the target URLare displayed, and you can infer the cause of the failure from this.
The same error code can have different causes depending on the screenshot, so first check which of the situations below the appearance on the screen most closely matches, then follow the guide for that situation.
Quick links to screen types in error screenshots
An access blocked message is shown. (CAPTCHA, bot detection, permission check, inaccessible, etc.)
Only a connection failure message is shown.
A popup window is covering the extraction area.
A login screen is displayed.
Only a blank screen with nothing is visible.
Only the main content is not visible.
[Group extraction] A normal screen with no issues is displayed.
[Scheduled extraction] A normal screen with no issues is displayed.
Error code - TimeOutException, TimeLimitExceeded
Error code - AutoClickError
Error code - ActionScriptError, ScriptError
✅ Step 3. If none of the above items apply?
Among the examples above, if none of the items apply or if it is difficult to accurately determine the cause from the error screenshot alone, [email protected]please contact us at.
Including the following information when contacting us will allow for faster and smoother support.
Please provide the URL of the data board failure screen. If it is group extraction, you may instead provide the URL of the group extraction result screen.
Please capture and send the screen that appears when you directly access the target webpage. Because the user’s access environment (country settings, login status, etc.) may differ from ours, please mark on the captured image (box, arrow, annotation, etc.) which location’s data you were trying to collect (element/area) so we can check more accurately.
Last updated
Was this helpful?