Skip to main content
The Bright Data Scraper Studio dashboard is where every scraper lives. Use it to inspect scraper properties, trigger runs, configure delivery, manage versions and review collection statistics. This page is a reference for every control you see on the My Scrapers page and the statistics drill-down.

The Scrapers dashboard

Every scraper you use, whether generated by the AI Agent, built in the Bright Data Scraper Studio IDE, or built by Bright Data teams, appears under My Scrapers on the Scrapers dashboard.
The My Scrapers page lists every scraper type, not only Scraper Studio scrapers.

Which scraper types appear on the dashboard?

The My Scrapers page lists three scraper types, distinguished by who builds and maintains each scraper.
TypeDescription
Scraper API700+ pre-built scrapers, built and maintained by Bright Data
Scraper StudioScrapers built and maintained by customers or AI
Scraper Studio ManagedScrapers built and maintained by the Bright Data team

What does each scraper status mean?

Each scraper and run carries a status that shows where it is in the build and collection lifecycle.
StatusDescription
ReadyThe run has been completed
CanceledThe run was canceled by the customer or system
ActiveThe scraper is saved to production and ready to initiate, but has not been triggered yet
DraftThe scraper is still being built and is not yet saved to production
RunningThe collection is running
To open a specific scraper’s dashboard, click the scraper.

What does the collection statistics page show?

The statistics page shows per-collection metrics for every run of a scraper. Statistics action menu Collector runs
ColumnDescription
IDUnique identifier for the collection job
TriggerWho triggered the job and how (API, UI, or schedule)
TemplateTemplate version number
InputsNumber of inputs submitted to the collection
RecordsNumber of records the scraper returned
Failed crawlsNumber of pages that failed to crawl
FulfillmentTotal number of unique pages discovered during scraping, including pages that were found but not necessarily scraped
Success ratePercentage of inputs that produced successful records
Queued atTimestamp when the job entered the queue
Started atTimestamp when the scraper started collecting
Finished atTimestamp when the scraper finished collecting
Job timeTotal job duration
Estimated time leftTime remaining for an in-progress job
QueueName of the queue the job is running in (from the trigger’s queue name)
Page LoadsTotal page loads consumed by the job
SpentTotal amount spent on this collection run

Collection run actions

The three-dot Actions menu includes the following options. Available actions may vary depending on the run status and delivery configuration. Three dots menu on a job row

Redeliver results

Use Redeliver results to send collected results again to the configured delivery destination. You can choose:
  • Dataset only — redelivers only the structured output data.
  • Dataset + media — redelivers the structured output data together with collected media files, such as images, videos, PDFs, or documents.
Use this when the original delivery failed, the destination was unavailable, or you updated the destination and want to send the same results again.

Rerun or cancel a collection

Use Rerun job to start a new run from an existing collection. You can choose:
  • Rerun all from beginning — starts a new run using all original input values.
  • Rerun failed pages — starts a new run only for pages that failed in the selected collection.
Use Cancel collection to stop an active collection before it finishes. Data already collected may still be available, depending on the run status and delivery settings.

Inspect results and errors

Use Quick view to preview up to 100 collection records in JSON format directly in the control panel. Use Errors to review failed inputs and error details. Use Activity to monitor a collection run over time. The page shows run status, start and finish times, success rate, crawl count, and performance charts. You can change the visible time range, such as 5 min, 1 h, 1 d, or all. The Activity page includes:
  • Run rate - shows how many pages were crawled, failed, or retried at each point in time, along with the success rate.
  • Pages - shows discovered pages, open pages, retriable pages, and pages currently being crawled.
  • Inputs - shows how many input rows were submitted and prepared for crawling.
  • Crawl rate - shows the system-calculated maximum number of allowed workers and the actual number of workers assigned to the run.
  • Crawl time per page - shows the average time spent crawling each page.
Use Activity to investigate slow runs, error spikes, retries, or changes in crawl performance.

Debug crawl

Use Debug crawl to investigate failed or unexpected scraper behavior.

How do I download the data from the dashboard?

Click the Download file options button, select a file format, and the download starts immediately.
Real-time job outputs are stored on Bright Data’s side but cannot be downloaded from the dashboard. To retrieve them, use the Scraper Studio API or send them to one of the delivery destinations configured in your delivery options.

How do I trigger a scraper and get results?

To trigger a scraper, use the three initiation options documented on Initiate collection and delivery: To retrieve results, click the three-dot icon on a scraper row and select Statistics to open the collection statistics page, where you can download the data.

Initiate collection and delivery

Configure trigger methods, file formats and delivery destinations

Scraper Studio IDE interface

Reference for every panel and control in the IDE