3.7 thinking causes the call to immediately end an...
# support
d
If you add thinking tokens for claude 3.7 the call ends as soon as a thinking block happens. However even worse is that now I can't delete the thinking tokens setting or even change the model to 3.5 so my agent in stuck in a completely broken state. Side note once you attach a workflow to an agent and then detact it, you can't ever get back to the non workflow UI either.
v
Hello Diirge, let me check on this with the team and get back to you.
> If you add thinking tokens for claude 3.7 the call ends as soon as a thinking block happens Can you share the call ID so I could take a look at what could've gone wrong for you? > . However even worse is that now I can't delete the thinking tokens setting or even change the model to 3.5 so my agent in stuck in a completely broken state. Can you record a loom video? This will help us understand what's not working for you and eventually get it fixed.
> Side note once you attach a workflow to an agent and then detact it, you can't ever get back to the non workflow UI either. When you change to VAPI provided module for workflow, we do show you a notification or an alert saying that you will lose all of your current prompt changes. So I don't see any issue here, just letting you know that it's an explicit action taken by you. https://cdn.discordapp.com/attachments/1351920140215648286/1352275432753336361/Screenshot_2025-03-20_at_7.08.47_PM.png?ex=67dd6c23&is=67dc1aa3&hm=18fc42251ed4587df3c2ac9d423a5941ee293fd6bb461ea312ecc18bee812a7b&
d
The issue is that once you remove it it’s not possible to ever get the UI back to the regular state
I don’t care that it removed my prompt. I cared that I tried the workflow builder and then it broke that assistant completely with no way to even modify the system prompt ever again. It gets stuck in the detached workflow UI
v
Can you share the assistant ID? I'll try to get your prompt.