Hello, I have a workflow which was working normally some days ago(id: 70489cc5-0504-4494-a3d6-b253a3740b22), but now has decided to crush(?) and just wait silently when it reaches 2 of my apiRequest nodes, instead of executing the apiRequest node like before. Here are some example call ids: 1: 76934164-41e8-4fee-809f-e97e9c457ef2 2: 28632a07-d8ce-4541-86d4-0f81ec8e7a5f If I make a call using other workflow (tried it with this one: 6e9358c3-6a4e-4d14-a697-64398a86d661) with exact same data, it executes the above apiRequest nodes fine and the call reaches the end. The API nodes in these 2 workflow are the same so there isn't any problem that would cause errors in the calls. Do you have any idea what could possible be wrong with my first workflow and the calls just remain silent instead of executing the API nodes like they used to a while ago?

Thanks for the details! To help narrow this down, have you checked the Call Logs or API Logs in the Vapi dashboard for the call IDs where the workflow hangs? Any error messages or tool execution results there would be very helpful for diagnosing the issue. [See dashboard debugging steps](https://docs.vapi.ai/debugging) Source: - [Vapi Debugging Documentation](https://docs.vapi.ai/debugging)

Ok, I followed all debugging steps, also made the node prompt as specific as possible to understand when to proceed to next nodes and worked!

Message marked as helpful by @Stefanos! 🎉

Hi, workflows is currently under development.