Jim has explained but here’s a little bit of context on how conflict resolution works
Conflicts are detected on push at the Sync Gateway side. The sync gateway rejects it with a 409 error.
Conflicts are resolved at the time of document save ( and in this case, that would be during replicator pull) and are automatically resolved by the system. You can override it with a custom conflict resolver.
So technically, this means that there are no conflicting revisions of a document in the database. That is by design.
So if you have a push-only replication and a document push is rejected because of a conflict, the local version of the document prevails. In other words, CBL will not keep trying to send up that document just so it can get rejected - it would be very inefficient to do so (remember that the sync gateway receive the document revision and reject it) because it is clear unless an attempt is made by the client to resolve it, the conflicting status of that document will not change.
If you expect conflicts in your system, you must use
pushandpull type replication.