How can I tell which node is causing my worflow to...
# support
k
I am trying to save a workflow, but every time it fails with a red pop up notification. I see in the docs that it says all nodes must be configured properly, but I cannot tell which node is causing the issue. Is there a way to see which node(s) are causing the save to fail?
v
Hi there! 👋 Sorry to hear you're having trouble saving your workflow. Unfortunately, I couldn't find information about a direct way to see which specific node is causing the save failure. However, I can definitely help you with several strategies to identify the problematic node! According to the [workflow documentation](https://docs.vapi.ai/workflows), "A workflow cannot be saved until every node is connected and configured. The system will not allow saving with any dangling nodes." Here are some approaches to help you identify the issue: ## Systematic Troubleshooting Approaches 1. **Check for Dangling Nodes**: Make sure every node is connected to at least one other node. According to the [documentation](https://docs.vapi.ai/workflows), dangling nodes will prevent saving. 2. **Review Recent Changes**: If the workflow was saving before, focus on nodes you recently added or modified. 3. **Examine Edge Conditions**: Issues with
AIEdgeCondition
,
LogicEdgeCondition
, or the new
FailedEdgeCondition
could be causing problems, as mentioned in the [changelog](https://docs.vapi.ai/changelog). 4. **Check Node-Specific Requirements**: - For
HttpRequest
nodes: Verify parameters are correctly configured to avoid "Bad request" errors as seen in [user reports](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1340615317772308520). - For function nodes: Ensure all required fields are included in your schema. Missing required fields can prevent saving, as noted in [community discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1326276427628154920). 5. **Use Workflow Tracking**: You can send a [
workflow.node.started
](https://api.vapi.ai/api#:~:text=ClientMessageWorkflowNodeStarted) message to track the start of each node, which might help identify where the workflow is failing, according to the [changelog](https://docs.vapi.ai/changelog/2025/2/17).
6. **Check for Variable Processing Issues**: Problems with variable processing in "Tool" blocks can lead to unexpected behavior, as reported in [community discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1324353725564715121). 7. **Examine Conditional Nodes**: Bugs in conditional nodes could be causing the save failure, according to [user reports](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341786285379162123). Is there anything specific about your workflow that might help narrow down where the issue could be occurring? Sources: - [Workflow Documentation](https://docs.vapi.ai/workflows) - [Vapi Changelog](https://docs.vapi.ai/changelog) - [Vapi Changelog 2025/2/17](https://docs.vapi.ai/changelog/2025/2/17) - [Discord Thread 1340615317772308520](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1340615317772308520) - [Discord Thread 1326276427628154920](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1326276427628154920) - [Discord Thread 1324353725564715121](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1324353725564715121) - [Discord Thread 1341786285379162123](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341786285379162123)
k
Is there a way to take the code version of a workflow and create the nodes from that? I currently have a complex workflow that I built, that I can't save, and I can't export, and when I check it in incognito none of my work is there. Can I copy over my work somehow so I don't lose it?
k
Hey Kai, As of now, what I understand is that there is some issue in the browser's local memory related to the VAPI dashboard, and eventually, all of your workflow state is stored in the browser's memory. If that's the case, then we cannot recover it. When you click on the Save button, it usually goes to the network request. You can try checking the network logs to see if you can find anything over there. If you still cannot find anything in the browser's memory, in the network logs, or in the local state, then sorry buddy, you have to do the rework again.
2 Views