The replication halt could be caused by one of the following:
Replication agreement disabled or nonexistent
Supplier missing the change record in its change log
Supplier change log cache corrupted
Replication manager using invalid credentials
Replication sending a thread in a halted state
Schema conflicts
Unallowed operation on the consumer due to Update Resolution Protocol (URP) conflicts
Network disconnection
Consumer state locked down by an unavailable supplier
Consumer out of disk
RUVs contain meaningless information, such as ffff, cleanruv