Urgent Error on the Conversation Node.
I'm facing a critical issue in VAPI that is affecting my clients' operations and likely impacting all other users outside the US as well.
When we create an agent (either through the dashboard or the API), a start node is automatically generated.
For workflows created via the API, this is a "trigger".
For workflows created within VAPI, it's a Conversation node with the "Start" tag.
(See the images for better understanding)
The problem is that only this first Conversation node, the one automatically created by the VAPI platform, has the transcriber working correctly in other languages.
For API-created workflows, the same issue occurs. Only the first Conversation node we add works in other languages.
In other words, if I want to build a flow in PT-BR (Brazilian Portuguese), I have to duplicate the "functional" Conversation node instead of simply adding a new one from the menu.
The biggest issue is that if I duplicate that node and try to use it as a global node, for example to transfer the call to a human, it does not work properly because the call starts on that node.
Watch this Loom video to understand the issue:
https://www.loom.com/share/aa958044f218449db528fda22d8cf0dd
So right now, if I want to build an agent in another language, the transcriber does not work, and I still do not have a proper way to transfer the call to a human.
@Shubham Bajaj
When we create an agent (either through the dashboard or the API), a start node is automatically generated.
For workflows created via the API, this is a "trigger".
For workflows created within VAPI, it's a Conversation node with the "Start" tag.
(See the images for better understanding)
The problem is that only this first Conversation node, the one automatically created by the VAPI platform, has the transcriber working correctly in other languages.
For API-created workflows, the same issue occurs. Only the first Conversation node we add works in other languages.
In other words, if I want to build a flow in PT-BR (Brazilian Portuguese), I have to duplicate the "functional" Conversation node instead of simply adding a new one from the menu.
The biggest issue is that if I duplicate that node and try to use it as a global node, for example to transfer the call to a human, it does not work properly because the call starts on that node.
Watch this Loom video to understand the issue:
https://www.loom.com/share/aa958044f218449db528fda22d8cf0dd
So right now, if I want to build an agent in another language, the transcriber does not work, and I still do not have a proper way to transfer the call to a human.
@Shubham Bajaj
