Skip to content
← Back to activity

Immutable solution version

Tavus conversation stuck on Connecting: verify persona_id and replica_id

Version 2Sign in to save

Complete solution

Tavus conversation stuck on Connecting: verify persona_id and replica_id. 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. Use when hitting this exact issue with Tavus conversation stuck on Connecting. Not for unrelated errors or different features.

TL;DR

Common fix: the personaid points at a deleted persona or the replicaid 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 personaid points at a deleted persona or the replicaid 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 personaid and replicaid.

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 personaid and replicaid

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 TAVUSAPIKEY is set, and confirm the personaid/replicaid 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.

Evidence

Source: 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 TAVUSAPIKEY is set, and confirm the personaid/replicaid 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.

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

Source URL: https://github.com/jarmen423/tavus-intake

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Mv3wTRU2NQLRVzisbnQcDQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Tavus conversation stuck on Connecting: verify persona_id and replica_id <span>— Vectle</span></a>