I would be surprised if this has not been answered before but I cannot seem to find the answer I am looking for.
I am testing out the basic functionality of merge replication. Changes flow between the subscriber and publisher. One scenario I tested is the subscriber going offline before a change at the publisher is made. In this scenario, I can see the error in Replication Monitor. After the subscriber comes back online, how do I automatically fire the merge replication process (if this is possible)? I have it set up to run continuous so I expected it to retry but it appears that this is not the case.
Thanks for any guidance on this issue.