before starting a big package update on NomadBSD-1.4, I created a boot environment (BE) before initiating the task
% sudo bectl create 2021-07-21_bf-pkg-upgrade
later I wanted to boot into this BE again
% sudo bectl activate 2021-07-21_bf-pkg-upgrade
But I ended up in the BE named
% bectl list
BE Active Mountpoint Space Created
2021-07-21_bf-pkg-upgrade R - 14.4G 2021-07-21 13:20
210414-225354 - - 3.14G 2021-04-14 22:54
nomadbsd-1.4 N / 4.58G 2021-04-14 22:32
also pressing  to the first boot-menu and choosing (the already chosen) 2021-07-21_bf-pkg-upgrade-BE still ended up booting the nomadbsd-1.4-BE???
The only way I can boot into my created BE is to rename the nomadbsd-1.4-BE to something else and rename my BE to nomadbsd-1.4
Is this behavior to be expected?