Why is my Cloud job slow or stuck?

If a Cloud job seems slow or stuck, first check whether it is queued or already running. The likely cause is different for each state.

If the job is queued

Your plan's parallel tasks determine how many scraping jobs can run at the same time. When all available tasks are in use, additional jobs wait in the queue until a task becomes available.

To check your current capacity:

1. Open Web Scraper Cloud.
2. Select Account Info in the top-right corner.
3. Check Parallel active tasks to see how many task slots are currently in use.
4. Check Scraping jobs in queue to see how many jobs are waiting to start.

Priority only changes the order of waiting jobs. Increasing priority does not add more parallel tasks and does not interrupt a job that is already running.

If the job is running slowly

Check the job configuration and sitemap behavior:

• Request interval: a higher value increases the time between page requests.
• Page load delay: a higher value makes Web Scraper wait longer before extracting data from each page.
• FullJS driver: runs pages in a browser environment and executes JavaScript, so it is generally slower than Fast.
• Scrolling and repeated clicks: long-running infinite scroll, Load more, or other dynamic interactions can keep a page processing for a long time.

Check for Empty or Failed pages

Open the job and check whether it is returning Empty or Failed pages. Web Scraper Cloud automatically retries these pages, so a job with many Empty or Failed pages can take longer to finish than expected.

If these counts are increasing, inspect the affected pages and fix the underlying access, page-state, timing, or sitemap issue.

Check for long-running JavaScript actions

Web Scraper Cloud has a 10-minute continuous JavaScript execution limit per URL. Long scrolling sequences or repeated dynamic pagination clicks can reach this limit and end with a JavaScript Timeout.

How Cloud parallelizes a large job

A single scraping job can also use additional available task capacity internally. When at least 250 URLs remain queued and slots are available, Cloud can split the remaining work into smaller parallel tasks. When fewer than 250 URLs remain, or no additional slots are available, the job continues processing normally.

What to change

• Use a Test scrape before changing timing settings for a full job.
• Reduce Request interval or Page load delay only if the target website still returns complete data.
• Use Fast when the sitemap is compatible and the website does not require JavaScript rendering or browser interactions.
• Review scrolling or click-based pagination if individual pages take an unusually long time to finish.

See the URL credits, parallel tasks and limits documentation and Run a Cloud scraping job documentation for more information.