Simulation Statuses

Every simulated call in Bluejay reports a status. So does every simulation run that groups those calls together. This page lists each one: what it means, why a call might land there, and what to do about it.

Two layers of status

Bluejay tracks status at two levels.

Simulation Result

One row per simulated call. Where the call is in its lifecycle, and if it failed, why.

Simulation Run

One row per group of calls launched together. Whether the group is still progressing or has finished. The pass/fail/cancel mix appears next to the status.

Simulation Result statuses

A simulation result is one simulated call. Its status moves through several in‑progress states before settling on exactly one terminal state.

In progress

These appear for a few seconds to a couple of minutes during a normal run. No action needed; they progress automatically.

Status	What it means
Initializing	The call has been created and is being prepared.
Queued	Waiting for a worker to pick it up.
Ready	For inbound Digital Humans (ones that receive calls). The Digital Human is online and waiting for your agent to call in.
Dispatched	The worker is starting the call. The phone hasn’t connected yet.
Running	The call is connected and the conversation is happening.
Evaluation Pending	We’ve queued your call for evaluation. Scoring will happen momentarily.
Evaluating	The transcript is being scored against your success criteria.

Completed

Status	What it means
Completed	The call ran end‑to‑end and was scored. Pass or fail against your success criteria appears separately.

Failure buckets

When a call doesn’t reach Completed, it lands in one of five failure buckets. Each one tells you who needs to do something about it.

No Connection: couldn't reach your agent

What happened: We couldn’t reach your agent at all. Common causes: bad credentials for your provider, a wrong agent ID, an unverified caller ID, an unreachable SIP destination, or your provider’s concurrency limit was hit before the call could connect.Who needs to fix it: Usually your config. Sometimes your provider’s plan limits.What to do: Click the row in the simulation results table to see the specific error code and message.

If it’s about credentials or agent IDs, check your integration settings in Settings → Integrations.
If it’s about concurrency, raise the limit on your provider account or stagger your runs so fewer calls go out at once.
If it’s about caller ID or SIP routing, confirm the number or destination is verified on your side.

Error codes you might see:

Group	Codes	What they mean
Provider authentication	`ELEVEN_LABS_AUTH_FAILED`, `RETELL_AUTH_FAILED`, `VAPI_AUTH_FAILED`, `WEBSOCKET_AUTH_FAILED`	Your provider rejected the API key Bluejay has on file.
Missing integration	`MISSING_ELEVEN_LABS_INTEGRATION`, `MISSING_RETELL_INTEGRATION`, `MISSING_VAPI_INTEGRATION`, `MISSING_PIPECAT_INTEGRATION`, `NO_PIPECAT_AGENT_NAME`	The provider integration isn’t connected to your organization, or isn’t fully configured.
Missing agent ID	`MISSING_ELEVEN_LABS_AGENT_ID`, `MISSING_RETELL_AGENT_ID`, `MISSING_VAPI_ASSISTANT_ID`	This Digital Human’s agent or assistant ID is empty.
Credential decryption	`ELEVEN_LABS_INTEGRATION_DECRYPT_FAILED`, `RETELL_INTEGRATION_DECRYPT_FAILED`, `VAPI_INTEGRATION_DECRYPT_FAILED`	We have credentials on file but couldn’t decrypt them. Usually fixed by reconnecting the integration.
Bridge connect	`ELEVEN_LABS_BRIDGE_CONNECT_FAILED`, `RETELL_BRIDGE_CONNECT_FAILED`, `VAPI_BRIDGE_CONNECT_FAILED`, `ELEVEN_LABS_SESSION_SETUP_FAILED`, `RETELL_SESSION_SETUP_FAILED`, `VAPI_SESSION_SETUP_FAILED`	The provider accepted the connection request but failed to start a session. Often a transient provider issue.
LiveKit session setup	`LIVEKIT_SESSION_SETUP_FAILED`	Bluejay couldn’t join your LiveKit room: the token webhook rejected our request or returned an unusable token, or the room join failed.
Telephony / SIP	`UNUSABLE_CALLER_ID`, `INVALID_PHONE_NUMBER`, `INVALID_SIP_DESTINATION`, `SIP_DIAL_FAILED`	The outbound call couldn’t be placed because the caller ID isn’t verified, the destination is malformed, or the SIP dial itself failed.
Concurrency and pre-start	`CUSTOMER_CONCURRENCY_LIMIT`, `BRIDGE_PRE_START_FAILED`, `NO_CONNECTION_TYPE`	Your provider’s concurrent-call limit was hit, pre-flight bridge setup failed, or the Digital Human has no configured connection type.

No Answer: reached the line but nobody engaged

What happened: We reached your phone number or SIP endpoint, but nobody engaged. Either nobody picked up, the call was rejected, or the agent hung up before speaking.Who needs to fix it: Customer side (your agent or your line).What to do: Confirm that:

Your agent is configured to accept calls from Bluejay’s caller ID.
Your agent is online.
Your phone or SIP routing is healthy and routes Bluejay traffic correctly.

Error codes you might see:

Code	What it means
`NO_ANSWER`	The phone rang out without anyone picking up.
`CALL_REJECTED`	Your agent received the call and explicitly rejected it (SIP 486 or 603).
`AGENT_HUNG_UP_BEFORE_SPEECH`	Your agent picked up but hung up before speaking.
`INBOUND_NO_INCOMING_CALL`	For inbound Digital Humans: the Digital Human waited for a call from your agent but never received one.

Call Dropped: call started, then died mid-conversation

What happened: The call connected and a real conversation started, but the line dropped mid‑call. Most often a provider‑side issue on your agent.Who needs to fix it: Customer side (your agent or your provider).What to do: The transcript up to the drop point is still available and gets scored normally, so you don’t lose data from before the drop. If you see a cluster of dropped calls in a single run:

Check your voice provider’s status page.
Review any recent agent config changes that may have introduced instability.

Error codes you might see:

Group	Codes	What they mean
Provider agent error	`ELEVEN_LABS_AGENT_ERROR`, `RETELL_AGENT_ERROR`, `VAPI_AGENT_ERROR`	Your provider’s voice agent reported an error mid-call.
Provider agent start failure	`ELEVEN_LABS_AGENT_START_FAILED`, `RETELL_AGENT_START_FAILED`, `VAPI_AGENT_START_FAILED`	Your provider’s agent failed to start its turn during the call.
Provider monitoring error	`ELEVEN_LABS_MONITORING_ERROR`, `RETELL_MONITORING_ERROR`, `VAPI_MONITORING_ERROR`	Bluejay lost the monitoring connection to your provider mid-call.
Bridge disconnect	`PIPECAT_CONNECTION_FAILED`, `BRIDGE_DISCONNECTED`	The audio bridge between Bluejay and your provider went down.

Out of Funds: Bluejay balance exhausted

What happened: Your Bluejay balance ran out before the call could complete.Who needs to fix it: Bluejay account admin.What to do: Top up your balance in Settings → Billing, then re‑run the affected calls.Error codes you might see:

Code	What it means
`INSUFFICIENT_BALANCE`	Your Bluejay account balance reached zero before the call could complete.

System Error: something inside Bluejay broke

What happened: Something inside Bluejay broke during your call. The evaluation pipeline, recording upload, or an internal service may have failed.Who needs to fix it: Bluejay.What to do: Ask in our Slack community to learn more about why your call failed. We log every failure and often have a fix in hand before customers reach out, so getting in touch is the fastest way to find out where things stand.

Cancelled

Status	What it means
Cancelled	You stopped the call before it started running. Only available while a call is still in the early stages (Initializing, Queued, Ready, or Dispatched). Once a call is actually running, you can’t cancel it; it will either complete or drop.

Simulation Run statuses

A simulation run is the group of simulated calls you launched together. Its status is simpler than the per‑call status: a run is either still happening or it has finished.

Status	What it means
Running	At least one call in the run is still in flight (queued, dispatched, running, or being evaluated).
Completed	Every call in the run has reached an end state, whether it passed, failed, or was cancelled.

The pass/fail/cancel breakdown appears alongside the status. A finished run might display:

Completed · 47 passed · 2 failed · 1 cancelled (out of 50)

A simulation run is Completed as soon as there’s nothing left to wait on. That includes runs where every call failed or every call was cancelled. The mix of outcomes lives in the counters next to the status, which keeps “is the run done?” a clean yes/no question.

Quick reference

If you see lots of…	Most likely cause	First thing to check
No Connection	Misconfigured integration or hitting a provider concurrency limit	Your provider’s API key, agent ID, and current concurrency setting
No Answer	Your agent isn’t picking up	Your agent’s phone routing, allowed‑caller‑ID list, online status
Call Dropped	Your provider is unstable for a window	Your provider’s status page; any recent agent config changes
Out of Funds	Bluejay account balance ran out	Your Bluejay billing settings
System Error	A Bluejay‑side problem	Ask in our Slack community. We often have a fix in hand before customers ask

For any specific failure, click the row in the simulation results table to see the exact error code, a detailed message, and a one‑click action where one is available.

Simulation Runs

How a simulation run is structured and how to launch one.

Simulation Results

How to interpret the metrics and per‑call data a completed run produces.

Getting Started

Key Concepts

Test

Monitor

Integrations

Two layers of status

Simulation Result

Simulation Run

Simulation Result statuses

In progress

Completed

Failure buckets

Cancelled

Simulation Run statuses

Quick reference

Simulation Runs

Simulation Results

​Two layers of status

Simulation Result

Simulation Run

​Simulation Result statuses

​In progress

​Completed

​Failure buckets

​Cancelled

​Simulation Run statuses

​Quick reference

​Related

Simulation Runs

Simulation Results

Two layers of status

Simulation Result statuses

In progress

Completed

Failure buckets

Cancelled

Simulation Run statuses

Quick reference

Related