Usually we'll only fetch active transaction history (via reading from config.transactions as a primary, but we have seen some cases where a service in the server can end up doing this briefly as a secondary when stepping down. This is fine conceptually since no writes will be able to occur once secondary, but it can cause this assertion to fail. Until we have a better solution for representing this state of being stepped down but not performing oplog application yet, we can just relax constraints for this read.