Simulation Table

Filter, review, and debug individual simulation runs.

Use the Simulation Table to review every individual simulation run.

It’s the fastest way to:

• spot failures

• confirm volume was executed

• open a single run for artifacts (video/screenshots)

Stuck or unsure? Click Request support (top right) to schedule a Google Meet with your dedicated campaign manager.

Where you’ll find it

You’ll see a simulation list/table in a few places:

• campaign dashboard

• a specific simulation group

• simulations view inside monitoring pages

What you’ll see in the table

Exact columns vary by goal and settings, but the table usually includes:

• Status (scheduled, running, successful, failed, paused)

• Created / started / finished time

• Campaign / simulation group

• Record identifier (primary key, if you configured one)

• Failure reason (for failed runs)

• Cost (when applicable)

• Device/browser (based on your simulation settings)

If you want stable record tracking, set a primary key in campaign configuration before uploading CSV data.

Status meanings

• Scheduled: queued to run based on your schedule and distribution.

• Running: executing in a real browser session.

• Successful: completed and matched your success criteria.

• Failed: completed but didn’t meet success criteria, or hit an error.

• Paused: intentionally stopped (campaign/group paused) and won’t run until resumed.

To understand one run deeply (artifacts + success logic):

• How to check simulation status?

Filter and debug quickly

1

Filter to Failed

Filter the table to Failed to see only problem runs.

2

Open a simulation

Click a row to open the simulation details.

3

Use the failure reason + artifacts

Read the failure reason first.

If enabled, open video and screenshots to see what blocked submission.

If you’re still stuck after watching the artifacts:

• Troubleshooting & Support

• How to request support?

Retry failed simulations

Retry is useful after you fix the root cause (mapping, automation, popups, success keyword).

• How to retry failed simulations?

Retries typically count as new simulations for billing.

Common patterns to look for

• Many failures at once usually means a config or page change.

• Only a few failures usually means bad input data for specific records.

• Sudden spikes in failures can indicate popups, rate limits, or success page changes.

Next:

• Campaign & Simulation Overview