Landscape Repository Profile Lost After Access Group Change

On standalone (on-prem) landscape web page, I created a new access group, and bulk assigned the new access group to several computers, landscape then generated a bulk activity to "apply repository profiles". The repository profile file for these computers in /etc/apt/sources.list.d/ was changed to .SAVE No new repository profile .LIST file was created. I had to manually move the .SAVE back to .LIST to restore the file. Seems like landscape wants to have a tight link between the repo profile and the access group, when it should not. My understanding is that the repo profile should be tightly linked to the Tag only. I assume if I remove any reference to the access group in the repo profile through landscape-api that this problem might go away. However, I don't think the Landscape software should care about that association.

OS:

Description: Ubuntu 18.04.5 LTS
Release: 18.04

Package details:

Unsure of specific landscape package that executes the landscape Web Server activities described above, so just used this landscape package to provide you with a reference:

$apt-cache policy landscape-common
landscape-common:
  Installed: 18.03~1075~git.256ad02~ubuntu18.04.1
  Candidate: 18.03~1075~git.256ad02~ubuntu18.04.1
  Version table:
 *** 18.03~1075~git.256ad02~ubuntu18.04.1 500
        500 https://archive.landscape.canonical.com bionic/main amd64 Packages
        500 http://ppa.launchpad.net/landscape/19.10/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status
     18.01-0ubuntu3.5 500
        500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
     18.01-0ubuntu3 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages