Normally one can wait for user activity on source database for reconcile to receive the desired message from next redolog and finish normally. However, at times this may involve long wait. If there are test tables in replication, one can always force a transaction on source database. If there are none, then as a workaround, one can issue a flush from source sp_ctrl as follows:
The flush will generate a message in Shareplex queues (due to Shareplex writing in redolog) that will make reconcile exit so that other maintenance activities can be performed.