When I use a playht voice provider, and I have an opening message with repeated content (eg Company 3 3 3) the opening message is not generated and / or is never spoken. Vapi returns no error, and the call logs seems to imply that it is trying to say the message. I have disabled the

formatPlan

in an attempt to resolve this, but it still happens. This happens with any re-occurance of the same word as little as two time. (eg "Hello and welcome to Company Company" will not generate) I can generate these messages with PlayHT api directly and it works fine Example calls: 40306184-7db0-46e1-9b6b-160529e596ea 31521060-9e52-4d58-8424-c2dcfa090d4c

Hi there! 👋 I understand you're having issues with PlayHT opening messages containing repeated content. Unfortunately, I couldn't find specific information about why PlayHT fails to generate or speak opening messages with repeated content like "Company 3 3 3" or "Hello and welcome to Company Company." However, I can share some relevant information that might help troubleshoot this issue. Based on the information I found, this could be related to voice provider caching mechanisms. According to [Discord conversations](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342338583721414677), the cache key is generated using a hash of the voice configuration, sample rate, and text content. Other users have experienced similar issues with different voice providers where changing the first message helped resolve caching-related problems. Some potential troubleshooting steps you could try: 1. Try tweaking the first message words - According to [user reports](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342338583721414677), slightly modifying the first message or using a different first message for some time might help clear the cache. 2. Check PlayHT configuration - Verify that your PlayHT API keys are correctly entered in the [VAPI Provider Key section](https://dashboard.vapi.ai/keys) and that your voice configuration is properly set up. 3. Inspect the call logs - The call IDs you provided (40306184-7db0-46e1-9b6b-160529e596ea and 31521060-9e52-4d58-8424-c2dcfa090d4c) can be analyzed further in the Vapi Dashboard under logs > calls to see if there are any clues about what might be happening. 4. Test with different patterns of repetition - Try different patterns of repeated content to see if there's a specific pattern that triggers the issue.

This isn't a caching issue, and I updated the opening message each time I attempted a potential workaround to ensure it was not cached. My playHT configuration is fine, as it works for my other calls, and I can generate a response from PlayHT directly. The call logs have been reviewed and do not provide any information. I have mentioned the pattern that re-creates this issue

Sorry for the delay. The team's on vacation, and your logs aren't showing up, so I can't look into it. Can we wait till Monday?

Hey Shubham, thanks for the update, please let me know when the team has had a chance to look into the error.

The development work on this bug has already been done, and it will be released when next back end changes are being deployed.