Whether you have hit “Run Extractor” manually, or set up a schedule, this is where the details of all you extractions will live, allowing you to review the details or your runs. Runs are organised in date order.
The icons on the left hand side indicate whether your run has:
Been interrupted (you’ve pressed stop):
Or it is in progress:
This will show you how many URLs were successful out of the total number that were queried. If there were failures, you can view the log file to understand what the reasons for the failures were.
This represents how long the run took to complete.
If you are querying multiple item pages, each URL will contain multiple rows, this will show you the total combined rows extracted by the run. For single item pages, each URL queried will return 1 row, so this should match the number of successful queries.
You can download the data from a given run in either CSV or JSON format from the run history.
The log file will show you a list of all the successful and failed URLs, so you can review what has gone wrong. There are a range of reasons this could happen, from simple 404’s, to the webpage being structured differently from the URL it was trained on.
If you want to see that the relevant data has been captured for your URLs, you can click “preview” For a quick glimpse of the first 100 rows.