How do non-continuous replications recover from connection loss?

Using Couchbase Lite .NET… if you start a non-continuous replication and then experience a network outage, how does the replication recover? Does it attempt to reconnect and finish the replication the same as a continuous replication would?

How do you know when a non-continuous replication is completely finished? Just by waiting for the replication to go idle?

Non-continuous should behave the same for connectivity issues like this. However, for transient issues like 503, etc, it will give up eventually instead of retrying endlessly. A non-continuous replication will never go idle, it will stop when it is finished so that is how you know.