-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prompt template configuration error #402
Comments
Running this locally gives me additional logs but I don't know if this is related to not noticing incoming calls at at container level 2025-01-23T08:38:43.324154Z [warning ] Maximum retries reached, stopping chat call.channel=voice call.id=e17aa4fb-f3a4-42fc-ba82-6b42808e09c1 call.message=hej förstår du mig på sven call.phone_number=+4570726774 |
I see exceptions (in red) in App Insights. Please share them. |
This is thrown by AI Translator API. The user you are using is not authorized to perform translation. Please fix your access key. |
I did change it to match in the local config.yaml by syncing, and I double checked that the translation has the correct password |
It seems you added the call-center-ai/app/helpers/config_models/prompts.py Lines 315 to 328 in 40d003b
If you want to add an explicit error in the prompt template parser, feel free to send a PR. |
This relates to the application trying to get a conversation object which doesn’t exists. This is surely related to the first error, which crashed the task responsible to persist the conversation object. First fix your configuration issue. |
I removed all the tokenized values "{}" and now the bot is able to speak, although the api-key error is still there but I don't know if that is a problem that affects the application or not, so I don't know if this needs to be fixed user@DESKTOP-H0LA0HR:/mnt/c/Users/loven/Software/call-center-ai$ make dev
|
Yes it requires to be fixed. It is used for conversation history translations, as you change languages, to avoid hallucinations. |
Event grids show my calls but the phone call doesn't reach anything and keeps trying to call
I have only added a prompt and language according to documentation, all services deploy correctly
This was to the container
This deployment was made with a full config-local-example.yaml which is not according to instructions but it did work yesterday
Seaching in application insights there is nothing indicating an exception except for Cosmos
normal_logs_no_signal.txt
The text was updated successfully, but these errors were encountered: