Understanding Run Types

DataIQ processes candidate data through different types of "runs." Each run type serves a different purpose, and understanding them helps you interpret what happened and whether any data was changed.

Simulation Run

Simulation runs provide a preview of proposed field changes without writing any data back to your ATS. Toro uses these to check field mappings and validate configuration — both for individual candidates and larger batches. No candidate records are modified during a simulation.

Real-Time Run

Once DataIQ is enabled, real-time runs happen automatically whenever new candidate activity is detected (a note, email, SMS, etc.). If a meaningful datapoint is identified, DataIQ evaluates it against current ATS values and updates the candidate's profile if an improvement is found.

Real-time runs typically occur within 15 minutes of activity being logged to your ATS. You'll see these happening at any time candidates are communicating with your team, including nights and weekends.

Historical Run

Historical runs process past activity to extract data from older messages, notes, or submissions. These are primarily used during initial DataIQ onboarding but can also be triggered for reprocessing after a system update or when acquiring an additional candidate database. Historical runs are triggered by Toro in accordance with your contract.

Parent and Child Operations

Parent Operations

When a historical run or simulation batch is triggered, DataIQ logs it as a Parent Operation. The parent holds the full group of candidates processed and links to the individual results.

Child Operations

Inside each parent are Child Operations — one per candidate. Each child shows the specific field changes, status, and details for that individual.