Replication Server can customize its response to data server errors.
If you want the Data Server Interface (DSI) to continue applying updates even when a data server error is encountered, use assign action at the Replication Server where the error class was created to change the error action from stop_replication to log or retry_log. All databases using the error class are affected. If the primary database for a class is at a different site, you may need to wait until the new error action is replicated to the local site.
To limit the change to one database, create a new error class with the create error class command. Specify the desired error actions for the class, then change the connection to the database to use the new error class.
To examine the commands in the transaction that caused the connection to be suspended, use sysadmin log_first_tran to write the first transaction into the exceptions log without skipping it.