## TL;DR

Common fix: the persona_id points at a deleted persona or the replica_id is from a different account - copy fresh IDs from the dashboard and retry. Open DevTools Network tab and look at the create-conversation response first; the error body names the bad field.

## Fix

1. Common fix: the persona_id points at a deleted persona or the replica_id is from a different account - copy fresh IDs from the dashboard and retry.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this Tavus conversation stuck on Connecting feature.
- The symptom matches: verify persona_id and replica_id.

## When NOT to use

- Unrelated Tavus conversation stuck on Connecting issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Tavus conversation stuck on Connecting.

## Variant phrasings

### verify persona_id and replica_id

## Why it happens

When a Tavus conversation lobby spins on 'Connecting' forever, conversation creation failed (community troubleshooting from the tavus-intake template). Check the browser console for API errors, verify TAVUS_API_KEY is set, and confirm the persona_id/replica_id in the config are real IDs from the dashboard. Also verify camera and mic permissions are granted - HTTPS is required for camera/mic in production.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.