conscious-sapphire
conscious-sapphire5mo ago

Tool calls (webhooks) in Workflow not working since 1 day. Same tools in Assistant work 100%.

No webhook call is done, it just idles in the workflow step.Call ID (there were multiple since yesterday, just providing one for reference): 534e7ad1-c88e-41f7-a8b8-02d43cd59cf8 Tiomestamp : 11.51 GMT+1 - Expected Tool to be executed. No respones, no webhook post / call went out as seen in the logs. It worked fine til Wednesday this week. I even built a new workflow but no chance, tools (webhooks) won´t execute.
29 Replies
flat-fuchsia
flat-fuchsia5mo ago
same here @Vapi Team
conscious-sapphire
conscious-sapphireOP5mo ago
Sorry, needed to more precise: I mean Tools->Functions (trigger an external webhook with a function in this case)
metropolitan-bronze
metropolitan-bronze5mo ago
Looking into it
flat-fuchsia
flat-fuchsia5mo ago
Any update? also having this issue ? @Kings_big💫
rare-sapphire
rare-sapphire5mo ago
same here
dependent-tan
dependent-tan5mo ago
Hey @Tomas Goldenberg @druxamb.base.eth can you share call ids?
flat-fuchsia
flat-fuchsia5mo ago
I've had several with the exact same case, here is the ID of one of them 2e9b3070-6202-4dbc-a2ad-ce8c914d7557 once the Workflow reach the tool node [It doesnt send the request, it doesnt even says the custom messages while executing, and it stops talking getting stuck in that node] Logs [LOG] [workflowStream] [conversation#conversation_1750275821414] AI edge met, conversation_1750275821414 -> saveQuestion1. Reasoning: user expressed readiness [LOG] [workflowStream] [tool#saveQuestion1] Started after that the workflow voice stops forever
genetic-orange
genetic-orange5mo ago
Same here
Shubham Bajaj
Shubham Bajaj5mo ago
Hey Aibaze Foundations Thanks for sending the call Eddy. Let me go through it and get back to you.
conscious-sapphire
conscious-sapphireOP5mo ago
Hi Shubham, I got another ID for you from just now. It is still not working, idling endlessly at the function call. Call ID: f5d7058b-0f96-4ac1-b850-2f8068f0d8da , Time Start: 21. Juni 2025, 14:42. Hope this helps in identifying the issue... Thanks!
flat-fuchsia
flat-fuchsia5mo ago
still happening with every tool in everyworkflow The tools work fine in assistants but not in workflows
rare-sapphire
rare-sapphire5mo ago
@Shubham Bajaj @Sahil Here's my workflow id 18c16662-ac96-4c0f-9944-954205cc84f5 error message (Meeting ended due to ejection: Meeting has ended)
rare-sapphire
rare-sapphire5mo ago
@Vapi Team same here
conscious-sapphire
conscious-sapphireOP4mo ago
I have some updates on this: This morning the browser call feature does not work in Workflows. So I tried again via assigned phone number. The workflow was reachable via the assigned phone number and IT TRIGGERED the function perfectly. However it was reacting very, very slow. So slow that it started to become unbearable. As of now webcall to test within vapi, without phone number does not work at all anymore. I can only guess, but maybe the function calls did not work due to webcall feature??? They seem to work though via phone call.
flat-fuchsia
flat-fuchsia4mo ago
@Vapi Team we need support here please a lot of us are experiencing this serious issue
dependent-tan
dependent-tan4mo ago
@Tomas Goldenberg @Sentinel @Aurimas @druxamb.base.eth @Aibaze Foundations @Playenzo Hey everyone, thanks for bringing up the concerns. Could you please try again? By now, the issue of Tools calls not triggering with your workflows should have been resolved. Please try making 2-3 calls and let me know how it goes. @Sentinel Could you share few call ID's related to this? @Tomas Goldenberg Can you also share the call ids and mention the issue which you are facing?
rare-sapphire
rare-sapphire4mo ago
I updated the workflow id, but it kept using the old voice assistant. I have tried clearing my browser cache
rare-sapphire
rare-sapphire4mo ago
conscious-sapphire
conscious-sapphireOP4mo ago
Shubham, the Web call feature works again, but still idles at function call! sharing more call IDs where it just idles at the function call (it always does): 395d7cd5-68f8-4035-9071-c9fec3172d01 and this one 395d7cd5-68f8-4035-9071-c9fec3172d01 and this one. I made a mini loom vid for you https://www.loom.com/share/e9aee6953d2d421aa6f49ad2aaee4871?sid=cff76dea-b877-49f0-88a5-c9e06e3effdd to show the idling issue at the function step - and also mention another problem with the language that sometimes the agent/workflow says stuff like "hold on a sec" during a function call, even though no messages are configured to the specific function. That is really disturbing when u have an agent that shall speak german and it falls back to english just in the function step. But lets focus on the idle issue first. Again, same workflow, same function called via linked phone line
Loom
Ölwechsel Terminvereinbarung und Tipps zur Fahrzeugpflege 🚗
Showing idling function call via webcall feature.
conscious-sapphire
conscious-sapphireOP4mo ago
Aurimas, try associating a phone number to your workflow and call it from a normal phone line. For me it works then with the tool call. Just not on the webcall. Workflow starts acting weird now for me, even in normal phone calls. It triggers the function but it randomly jumps to modules that come far later in the flowchart all of a sudden?? Is Vapi working on it in the background ?
dependent-tan
dependent-tan4mo ago
Hey @Sentinel l, could you please share the call_id related to this along with the Loom video? Thanks for sharing the video earlier. I assume it has been resolved from your new comments. @Aurimas genuinely appreciate you sharing the Loom video. I noticed that you haven't shared any call ID until now, so I couldn't determine this new call ID from your previous call ID by accessing your Org ID. If you could share the call ID, I'd be able to review its call logs and identify the cause of this issue.
conscious-sapphire
conscious-sapphireOP4mo ago
Hi Shubham, the one from the loom yesterday was: Call ID 28df9ba7-e0db-4eb6-a3ca-272b505f000f at 11:38 o´clock local time. However I just tried via webcall and it triggered the function. It seems to work again!!! Here are two call ID s where it just worked a couple of minutes ago: Call ID 30617c9b-00f3-40c7-8613-13cfd8350ca9 & Call ID ce4da4c1-fe50-4ecf-9610-724b3786d3ad I will keep testing. I can confirm, function calls work again with webcall feature!👍
rare-sapphire
rare-sapphire4mo ago
@Shubham Bajaj ?
flat-fuchsia
flat-fuchsia4mo ago
They are working for me now !
dependent-tan
dependent-tan4mo ago
@Aibaze Foundations @Sentinel I'm glad it's working for you. Hey @druxamb.base.eth , this issue has been fixed. Could you please try again and let me know if it doesn't work? If it doesn't, please share the call_id and timestamp.
rare-sapphire
rare-sapphire4mo ago
I screen recorded with loom, but the console didn't show in the video. https://www.loom.com/share/a5707214eafb46269b587fcbbb9917f3?sid=c8793320-a7ee-45df-93d2-30ae9e904429 workflow id: 18c16662-ac96-4c0f-9944-954205cc84f5
No description
rare-sapphire
rare-sapphire4mo ago
@Shubham Bajaj @Jordan @Sahil ?
dependent-tan
dependent-tan4mo ago
To pass the workflow id to the Web SDK, you need to include it as the fourth parameter. The first parameter is reserved for the Assistant id, the second for the transient assistant, and the third for the score id. Therefore, you should pass the first three parameters as NULL, and then the fourth parameter with the workflow id. This will ensure that the request is processed correctly.
rare-sapphire
rare-sapphire4mo ago

Did you find this page helpful?