Feature description

If the webapp fails to communicate with the database when saving our flow, it won't be able to do so and you have to rewrite your whole flow since last revision.
I went in a case where it said 404 Not Found when saving the flow (no idea why) and it was a total loss of time to rewrite it all back again.

My suggestion is to add an auto-save which would save the flow in a tmp state with a feedback on the client-side when it lose connection. This issue is quite annoying IMO especially since the flow has to be validated each time you want to save and it would lead to a non-sense revision if you would save as you would in an IDE.
That's why I think it should be considered apart from the revisions and allow the user to restart from this tmp state once he comes back to editing the flow.

I might give a try to this

After some testing, found out that the webapp is properly handling issue trying to reach backend.
I can't reproduce the issue 404 I had previously. I suspect it to happen only when using server standalone when the server is under heavy load which leads to unresponsive webapp.

I'm wondering if this issue has any sense till I find out how to reproduce the issue.
My tests showed that if unable to reach backend, the user remains on the same page with its current modifications.

The only improvement I can think of is adding a pop-up to show the user there was an issue ? It is currently showing a progress bar at the top completing and then nothing happen