Check the results of your scrapers with this flexible checker. Just supply a dataset or key-value store ID and a few simple rules to get a detailed report.

Id of dataset or key value store where the data are located.

Apify Storage ID

You can change number of loaded and processed items in each batch. This is only needed if you have really huge items.

Batch Size

Custom object where you can put any value that will be accessible in functional checker functions as **third** parameter. Useful for dynamic values coming from other actors.

Context

Function that returns an object with item fields as keys and values as predicates (functions that return true/false)

Functional Checker

You can specify which fields should display in the debug OUTPUT to identify bad items. By default it shows all fields which may make it unnecessary big.

Identification Fields

How many items will be checked. Default is all

Limit

Sets how big report you get for each unique combination of bad fields. Keeping this small and running it again after fixing some is the best approach. It speeds up the actor and reduces memory need.

Max bad items saved

You can specify minimal success rate (0 to 1) of any field. If the success rate will be higher than this, the field will not be count as bad field. This needs t obe an object with fields as keys and success rate as values.

Minimal success rate

If checked on, the actor will consider extra fields as bad fields. Uncheck if you don't mind them

No extra fields

From which item the checking will start. Use with limit to check specific items.

Offset

Raw Data

Only specify if Apify storage id points to a key value store! This is the record key under which the data are.

Results Checker

Where next?