When resharding aborts, it stores the abort reason in the coordinator document. If it steps down and restarts again, it will abort the cancel token when it sees that the state is aborting. This in turn will cause it to get callback cancelled error later (I suspect from here) and the resharding coordinator will treat it like the user aborted resharding and return the generic ReshardingAborted error code instead of the original error code.