Summary
GitHub Issue Summary
Problem Statement: Voice filesearch GPT is failing in node 9db9 of the active flow after a webhook migration.
Expected: The voice filesearch GPT function should execute successfully and process audio inputs without errors.
Actual Result: The user received a "Timeout: taking long to process response" error when testing the flow for a specific contact.
Error Messages:
- "Timeout: taking long to process response"
Reproduction Steps:
- Update the existing active flow according to the speech webhook migration.
- Test node 9db9 with the relevant audio input for a contact.
- Observe the error message indicating a timeout.
Additional Context: A different contact (ID: 1966613) tested successfully, while contact ID 2336280 encountered the failure. Screenshots related to the issue were provided but are not included in this summary.
Source
Original message
Hi <@937979788587597824> <@1132952719586492478>
I have updated our active flow https://ndrcsupport.glific.com/flow/configure/e7929964-9106-4b71-8689-29374349c96d as per the speech webhook migration. During testing, I found that voice filesearch gpt is failing. node 9db9 in the above flow. can you please check on priority
Full thread transcript
.soumya_m: Hi <@937979788587597824> <@1132952719586492478>
I have updated our active flow https://ndrcsupport.glific.com/flow/configure/e7929964-9106-4b71-8689-29374349c96d as per the speech webhook migration. During testing, I found that voice filesearch gpt is failing. node 9db9 in the above flow. can you please check on priority
Glific AI doc bot (bot): Hi there! Thanks for flagging this. I can’t access your flow link from here, so I do not have sufficient info to answer this question. <@&1383715800632004648>, can you please chime in here? Also, could you share the flow name?
Meanwhile, please paste the exact error from Flows > Webhook logs for node 9db9, along with the test contact and timestamp so we can trace it quickly .
For voice-filesearch-gpt, double-check that the node’s Function is set to voice-filesearch-gpt and the Function Body includes contact=@contact, assistant_id, speech mapped to the audio result you captured, plus source_language and target_language .
If you expect a voice reply, confirm your org is linked to Google Cloud Storage; without GCS the voice/media output can fail to generate .
If you customized TTS settings, note that provider and model must be set together; setting only one will throw a webhook error .
Docs: Speech to text capabilities in Glific, Text to speech capabilities in Glific, ChatGPT using OpenAI APIs, Glific Webhooks (logs).
Glific AI doc bot (bot): Was this helpful in resolving your query? Or do you need further support?
Glific AI doc bot (bot): Thanks for letting us know! <@&983219484091383888> has been notified and will assist you shortly.
.soumya_m: "Timeout: taking long to process response" - this is the error <@1132952719586492478>
sangeetamishra._91310: <@1118428955859505224> - I tested this flow and for me it worked fine https://ndrcsupport.glific.com/chat/1966613
But for contact id https://ndrcsupport.glific.com/chat/2336280 the node failed logged an issue and went to another flow. I have added screenshots for reference.
Summary
GitHub Issue Summary
Problem Statement: Voice filesearch GPT is failing in node 9db9 of the active flow after a webhook migration.
Expected: The voice filesearch GPT function should execute successfully and process audio inputs without errors.
Actual Result: The user received a "Timeout: taking long to process response" error when testing the flow for a specific contact.
Error Messages:
Reproduction Steps:
Additional Context: A different contact (ID: 1966613) tested successfully, while contact ID 2336280 encountered the failure. Screenshots related to the issue were provided but are not included in this summary.
Source
Original message
Hi <@937979788587597824> <@1132952719586492478>
I have updated our active flow https://ndrcsupport.glific.com/flow/configure/e7929964-9106-4b71-8689-29374349c96d as per the speech webhook migration. During testing, I found that voice filesearch gpt is failing. node 9db9 in the above flow. can you please check on priority
Full thread transcript
.soumya_m: Hi <@937979788587597824> <@1132952719586492478>
I have updated our active flow https://ndrcsupport.glific.com/flow/configure/e7929964-9106-4b71-8689-29374349c96d as per the speech webhook migration. During testing, I found that voice filesearch gpt is failing. node 9db9 in the above flow. can you please check on priority
Glific AI doc bot (bot): Hi there! Thanks for flagging this. I can’t access your flow link from here, so I do not have sufficient info to answer this question. <@&1383715800632004648>, can you please chime in here? Also, could you share the flow name?
Meanwhile, please paste the exact error from Flows > Webhook logs for node 9db9, along with the test contact and timestamp so we can trace it quickly .
For voice-filesearch-gpt, double-check that the node’s Function is set to voice-filesearch-gpt and the Function Body includes contact=@contact, assistant_id, speech mapped to the audio result you captured, plus source_language and target_language .
If you expect a voice reply, confirm your org is linked to Google Cloud Storage; without GCS the voice/media output can fail to generate .
If you customized TTS settings, note that provider and model must be set together; setting only one will throw a webhook error .
Docs: Speech to text capabilities in Glific, Text to speech capabilities in Glific, ChatGPT using OpenAI APIs, Glific Webhooks (logs).
Glific AI doc bot (bot): Was this helpful in resolving your query? Or do you need further support?
Glific AI doc bot (bot): Thanks for letting us know! <@&983219484091383888> has been notified and will assist you shortly.
.soumya_m: "Timeout: taking long to process response" - this is the error <@1132952719586492478>
sangeetamishra._91310: <@1118428955859505224> - I tested this flow and for me it worked fine https://ndrcsupport.glific.com/chat/1966613
But for contact id https://ndrcsupport.glific.com/chat/2336280 the node failed logged an issue and went to another flow. I have added screenshots for reference.