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.

same here @User

Sorry, needed to more precise: I mean Tools->Functions (trigger an external webhook with a function in this case)

Looking into it

Any update? also having this issue ? @Kings_big💫

same here

Hey @Tomas Goldenberg @druxamb.base.eth can you share call ids?

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

Same here

Hey [Aibaze Foundations](https://app.plain.com/workspace/w_01HYEQ5FKPH8CPX2MS608B6S51/customers/c_01JWED0WZM04NWZJW8YP2NF21A/) Thanks for sending the call Eddy. Let me go through it and get back to you.

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!

still happening with every tool in everyworkflow

@User @User Here's my workflow id 18c16662-ac96-4c0f-9944-954205cc84f5 error message (Meeting ended due to ejection: Meeting has ended)

@User same here

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.

@User Team we need support here please a lot of us are experiencing this serious issue

@Tomas Goldenberg @AiforYou @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.

I updated the workflow id, but it kept using the old voice assistant. I have tried clearing my browser cache

@Shubham Bajaj still the same. sharing a loom video with the problem: https://www.loom.com/share/f91b2c8d71124eb7b3cd81956dddce7d?sid=1c3de66e-ea3a-4d49-a404-5e60fe835132

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

Hey @AiforYou 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.

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.

@Shubham Bajaj ?

They are working for me now !

@Aibaze Foundations @AiforYou I'm glad it's working for you.

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 https://cdn.discordapp.com/attachments/1385560608853852200/1389329830847451238/image.png?ex=686439bc&is=6862e83c&hm=ac15cdaa4caf86ebae4ee93bd32946be73f552d7c5e864ec0137ac535a57c852&

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.

I already responded to you in this thread https://discord.com/channels/1211482211119796234/1385998823603568820