If the option to delete files on revert is enabled, the revert operation causes incorrect file state in the perforce cache
It looks like it has some code to handle this when the option to delete is disabled, but not for when the option is enabled.
Expected -> File is reverted in perforce, deleted from disk, and internal state is set to EPerforceState::NotInDepot
Actual -> File is reverted in perforce, deleted from disk, and internal state is EPerforceState::MarkedForDelete
MarkedForDelete is the state when you want to delete a file from the depot, but in this case the file was never in the depot, so should be set back to not in depot
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-169928 in the post.