Hey @fuska70 , thanks for providing the details and the Agent ID. Let me check this with the team, and I’ll get back to you with an update as soon as possible.
We have also tried adding override_agent_version: 2 and override_agent_version: 3 but the result is the same — the call always uses the old published prompt (v2.6) instead of the updated one (v2.7).
The agent shows is_published: false and base_version: 3 via the GET agent API, even after calling publish-agent-version with version 2 and 3.
The Test Audio in the dashboard works correctly with the new prompt, but outbound API calls always use the old one.
Hey @fuska70 Just checked with the team, the agent itself is publishing correctly. Latest published version on agent_c0cd0840fd60882f793ebb629f is v99 (isPublished: true). The actual issue is on the phone-number side has its outbound agent pinned to agent version 81, so every call from POST /v2/create-phone-call loads that old version regardless of how many times you republish.
Test Audio works because it resolves the agent’s latest published version directly, bypassing the phone-number binding.
Fix: in the dashboard, open Phone Numbers → Outbound Agent, re-select Sofia and save set the version dropdown to “Latest” so future publishes flow through automatically. Or via API: PATCH /update-phone-number/ with the outbound agent’s version set to 99 (or the version you want).
About is_published: false and base_version that’s the in-editor draft, which is expected. Drafts always carry isPublished: false and a baseVersion pointing at the version they were forked from; the published row (v99) carries isPublished: true. There isn’t currently a “publish via API” endpoint publishing is a dashboard action that creates a new version record.