I've gone node by node and can't find anything unsaved, however, when I do try to save I get an error message 'Save Failed' 'Failed to save workflow. Please try again' and then continue to show unsaved changes at the top. Is there a way for us to see what the errors are or which nodes are 'unsaved'? https://cdn.discordapp.com/attachments/1357733839300071515/1357733839954513961/Vapi_Unsaved_Error.png?ex=67f147ac&is=67eff62c&hm=b4713532e61540852e295ae1a92c434b86a4e62c6836624a37befd59fd6f2028&

Hi saulgoodman40472, maybe related to known issues with the UI today ... vapi devs are on it in a moment according to this: @Sahil just posted an update at https://discord.com/channels/1211482211119796234/1357671691412836432/1357729583788724365

Hi there! 👋 I understand how frustrating it can be when you're getting a "Save Failed" error despite checking all your nodes. Unfortunately, I wasn't able to find specific information about how to directly view which nodes are causing the "Save Failed" error in the Vapi UI. However, I can definitely help with several troubleshooting approaches that might resolve your issue! ## Potential Causes & Solutions ### Check Workflow Requirements According to [Vapi documentation](https://docs.vapi.ai/workflows), a workflow cannot be saved until every node is connected and configured properly. The system won't allow saving with any dangling nodes. Make sure: - All nodes are properly connected - No nodes are left disconnected - All required fields in each node are filled out ### Try These Browser-Related Fixes Several users have reported similar issues that were resolved by: - Refreshing the page to see if the notification clears - Clearing your browser's cache and cookies - Trying an incognito browser window - Disabling browser extensions that might interfere - Using the browser's developer console (F12) to check for any error messages that might provide clues ### Known UI Bugs & Workarounds There are some known bugs in the Vapi UI that can prevent saving: - Some users have reported issues specifically with saving headers in the UI - As a workaround, you can use the API to add tool headers instead of the UI - The API documentation is available at [https://docs.vapi.ai/api-reference/tools/create](https://docs.vapi.ai/api-reference/tools/create) ### Check for Syntax Errors Errors in syntax or issues with variables can cause saving problems: - Verify that all variable names are spelled correctly - Ensure variables match those provided in parent blocks - Check for any additional syntax errors in your JSON or code ### Recent Platform Changes If this workflow was working before: - There might be ongoing migrations in the Vapi platform affecting functionality

Fixed.

not yet ... do i have to wait a specific time before the fix is in effect?

I'm still having the issue. Is there a way for us to see what issues are preventing the workflow from saving? Or to see what 'unsaved changes' there are?

maybe the system is "liing"?

Meaning there aren't really unsaved changes?

I mean take this with a lot of precaution but: Is everything working as it should? What happens when you refresh the page? Stays everything the same? BTW: Do you use deepgram as a transcriber?

@Sven I am using deepgram. Also, I just updated the global prompt. It gave me the same error message and said it couldn't save it. I went to a different scree, refreshed, went back and it did save. Maybe it's a cache issue. I will try logging in incognito.

Marking this ticket as Solved ✅