My first squad member has 3 destinations. I can trigger the first two, but I cannot trigger the third even by speaking the exact text contained in its description. Call Id: aa342a39-ceee-4fe1-8a79-3c119dabc4c5 https://cdn.discordapp.com/attachments/1280496708517630065/1280496708781998183/Acme_SQUADs_4_Members.json?ex=66d84afd&is=66d6f97d&hm=e45351d1a1f66ce1a72dddb1fc64dfed7647248b70c0ad7354a0a8d89bfbee39&

@ACME Mike I'm sorry to hear that you're experiencing issues with triggering the third destination in your squad member's configuration. To assist you better, could you please provide me with the exact text you're using to trigger the third destination, as well as any error messages or unusual behavior you're noticing when you attempt to trigger it? This information will help me understand the issue more clearly and provide you with the appropriate support.

try disabling semantic cache.

Thanks...disabling semantic cache seemed to make no difference. I added instruction to the system prompt to "hand off the user when..." and it's transferring good so far for now. I thought it would transfer just based on the destination descriptions alone - in my case it needs more instruction.

I've seen you mention semanitic cache before... Can you explain what this is? I don't see any reference to it in the API documents.

for serving responses we cache your responses.