Fails back to closed state on failure to check state after calling open API?

[sjefferson99]

Observed behaviour tonight where I adjusted space state from closed to open for 4 hours, but it took a while to try and apply space state and said API was slow. It then finally said space state was closed and did so for a few more seconds, it then updated to space open.

It would have been likely that someone would have then tried again and therefore submitted space open twice.

Need to check if it's possible that a space state change to open could drop back to closed if the right API failure/space state failure directly after occurred.

Correct behaviour should be not changing state unless a definite response received from server and to otherwise stay in updating/error state, also ensure no paused checks get applied after state change i.e. space closed received, but paused as updating state, then applied when API call timed out.