What Is a Simulation Run?
A Simulation Run represents one execution instance of a specific simulation scenario. When you initiate a simulation run, Bluejay’s digital humans engage your voice agent through realistic phone call interactions. The run tracks every call from start to finish and records the data needed to evaluate performance.Run Lifecycle
Every simulation run moves through a predictable set of stages:- Queued — The run has been submitted and is waiting for available capacity.
- In Progress — Digital humans are actively calling your voice agent and interactions are underway.
- Completed — All calls in the run have finished and results are ready for review.
- Failed — The run could not complete due to a configuration or connectivity issue.
Run Structure
A simulation run is composed of the individual calls placed by each digital human in the simulation. The run record includes:- Run ID — A unique identifier for referencing this execution.
- Simulation Reference — The parent simulation the run belongs to.
- Timestamp — When the run was initiated.
- Call Count — The total number of calls placed during the run.
- Status — The current lifecycle stage of the run (queued, in progress, completed, or failed).
Initiating a Run
You can start a simulation run from the Bluejay dashboard or programmatically through the API:- Dashboard — Navigate to your simulation and click Run Simulation.
- API — Use the Queue Simulation Run endpoint to trigger a run for voice simulations, or Queue SMS Simulation Run for SMS-based scenarios.
Best Practices
- Run frequently — Execute simulation runs on a regular cadence so you can detect regressions early.
- Compare across runs — Use run timestamps and IDs to track how your agent’s behavior evolves over successive executions.
- Automate via API — Integrate simulation runs into your CI/CD pipeline or scheduled workflows to keep testing continuous.