If the replica set config is invalid (missing recipient nodes, etc) we currently set the decision promise to kAborted and immediately return without updating the state document. This means we leave the state document in its initial state. Therefore if the current primary steps down, the next primary will try to "resume" the operation using this stale state document. It also means other shard split might not be able to work as there currently is an "active" shard split.