Hey there @mike.edwards!
As far as I’m aware, this is expected behavior due to the fact that scopes shouldn’t be altered once the authorize request has already been made - In this case you are attempting to append a scope to a token which has already been created.
Instead, you might look into adding a custom claim using the same metadata. This way you can be sure. it’s not interfering with anything else.
Hope this helps!