This bug might be related to a similar issue with CCLI licencing.
To reproduce:
Result:
Expected result:
Looks like this bug was logged about a year ago and fell through the cracks. Thanks for the reminder