I am using the workflow and the agent doesn't follow the flow and starts at random parts of the flow. It seems like a potential cache issue. If I cut a call short, the next call picks up where that past one left off instead of starting the workflow from the start.

Hi there! 👋 I understand you're experiencing an issue where your agent doesn't follow the workflow correctly and seems to pick up from where previous calls left off instead of starting fresh. This definitely sounds frustrating! I'm happy to let you know that I found information about this exact issue. According to information I found, the Vapi support team is currently investigating this specific problem where "the agent doesn't follow the flow correctly and picks up from a previous call, which is potentially a cache issue" [(Discord thread)](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336607973576933420). You're not alone in experiencing this - other users have reported similar issues where agents provide random answers or don't follow the defined workflow as expected. While I don't have specific troubleshooting steps for this particular caching issue, it appears to be a known problem that the Vapi team is actively working on. Some users have tried general troubleshooting steps like clearing browser cache or recreating assistants, but since this appears to be a server-side issue, those may not fully resolve the problem. Is there anything else about this issue you'd like to know, or can I help with any other questions about Vapi workflows? Sources: - [Discord thread about Vapi workflow caching issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336607973576933420) - [Discord thread about agent not following workflow](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1343607310102040798)

Thank you, any idea where this setting is?

Visit here for more guides https://docs.vapi.ai/workflows

Oh yes, this is exactly what I've done and follow their instructions perfectly. Non workflow assistants work perfectly, but the workflow assistant performs terribly with all sorts of caching issues and starting the conversation from various nodes many times skipping the first node

Make sure to properly end each call session and reset the workflow state before starting any new calls..