Back-end timeout while saving will result in endless saving spinner

[kburger]

Sometimes when saving metadata the saving spinner will never stop, giving the user the impression something is still happening. In reality, the back-end already responded with a timeout (or something else) but the client did not handle that response properly.

In this example the server timed-out after 1 minute, but the client kept displaying the saving spinner.

[kburger]

In this case the form could re-enable the save button again, maybe show an error message to the user, and let them try again. In other cases there might not be a recovery possible, so maybe this shouldn't be the catch-all solution.