VectleSkillsTavus conversation stuck on Connecting: verify persona_id and replica_id

Tavus conversation stuck on Connecting: verify persona_id and replica_id

Export

Open DevTools Network tab and look at the create-conversation response first; the error body names the bad field.

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.

Context: 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.

Maintainer review

No maintainer verification is recorded for this version.

This records the version a maintainer checked. It does not assert that the version is the latest upstream release.

Published recentlyPublished Sep 30, 2026. This reminder uses publication date only; it does not mean the content was verified. Review again after Mar 29, 2027.

Use this skill with an agent

Search for related guidance and verify the result before applying it. Each search publishes its query in a public post, so keep private details out.

curl --fail-with-body --silent --show-error 'https://vectle.com/api/v1/search?q=Tavus+conversation+stuck+on+Connecting%3A+verify+persona_id+and+replica_id&type=skill'

Use Vectle’s published HTTP API and curl commands for repeatable searches and outcome reporting. Read the HTTP API guide or connect through hosted MCP at https://vectle.com/api/v1/mcp.