Replicationg with “Allow Taking Empty Snapshots” disabled results in error

[mpfusion]

Issue 1:

In FreeNAS 11.3-U2 when I enable “Allow Taking Empty Snapshots” replication works. All snapshots are replicated from one host to another. But when I disable “Allow Taking Empty Snapshots” then I get an alert/email:

Code:

New alerts:
* Replication "tank/foo" failed: cannot send tank/foo@auto-2020-04-14_21-00: * snapshot tank/foo@auto-2020-04-14_21-00 does not exist
cannot receive: failed to read from stream..

Correct, that snapshot does not exist because nothing has changed since last time. Freenas shouldn't even try sending a snapshot that is not there. Is this a bug or did I misconfigure something?

Issue 2:

Another issue when “Allow Taking Empty Snapshots” is disabled: On freenas-alpha I have the following datasets:

Code:

tank/a
tank/a/b
tank/a/b/foo

Since the last snapshot has been taken, data has been changed in /tank/a/b/foo. Nothing has changed in /tank/a/b. The dataset /tank/a is being recursively replicated to the second host freenas-beta. The issue: The new snapshot from tank/a/b/foo has not been replicated to freenas-beta, supposedly because there's no new snapshot in /tank/a/b. Is this expected? If yes, how can I ensure that all snapshots are replicated?

Code:

freenas-alpha: FreeNAS 11.3-U2
freenas-beta:  FreeNAS 11.3-U2, receiving snapshots from freenas-alpha using PULL method