Error saving workflow
# support
p
My workflow f2b8c4a9-b60f-4171-98dc-bcc1d96168eb threw a "Save Failed" error after my most recent edits (it had been saving up until about 15 minutes ago). The edits in fact do save; ive logged out and back in, and the edits are up to date, but I cannot run a test call because the workflow insists there are unsaved changes. Org ID ba4dc554-da46-4e8a-bde5-137541e4f3b2
**when i open Vapi on a different browser, none of my edits from the entire day are stored. Must be caching my edits somehow.
is there a way to edit the workflow code directly or is the code view only?
k
It sounds like the workflow is locally caching your edits, which is why you're seeing them in one browser but not another. This typically happens when the frontend gets out of sync with the backend. That’s also why it’s showing as unsaved and preventing test calls, even though the edits appear to be there. Right now, workflow code is view-only, so there’s no way to manually patch or force-save from the code editor. Have you tried Duplicating the workflow? This has happened to me before as well. This should reset the save state and clears any stuck cache issues.
p
I duplicated the workflow and it did work for the meantime, but it appears that by updating and saving one particular node (say_1745265050825) I am triggering the Save Failed error.
@User is there a bug in saving workflows? I'm getting the same error in multiple browsers and when using incognito
k
Currently we are working on resolving the issue
p
@User how is this issue going?
k
Not yet