Thanks for shedding light on the culture of using Blocs. But if I may suggest, there should be no concept of "temporary state" since that means we haven't really understand a state machine. A proper way is to always have an action to change state and that will make the state machine diagram clearly show what are the actions are and the transitions between states. For example, when changing state from UserInitialFetching to UserInitialFetchingError, the action is clearly shown as an "error" action. But from UserInitialFetchingError to UserInitialized, there is no action. So it should be fixed by adding a new action, let's call it, "error handled" action.