Dependencies in a group

I have a group of java projects which supply features to be used as dependencies by implementations.
This has been working well until recently, when I added a new feature which is currently only used by one new implementation.
When the implementation requiring the new feature builds using ${CI_JOB_TOKEN} the error ‘status code: 403, reason phrase: Forbidden (403)’ occurs against the new feature’s jar
The ci_settings was updated to use a created Group-Token. The error changed to ‘status code: 401, reason phrase: Unauthorized (401)’ occurs against a different feature in the group’s jar

Is it possible the new feature is not in the group with the others previously built and deployed? How can I tell?
Using the ‘Deploy → Package Registry’ section for the folder that the group is based upon shows all the expected .jar files.
I note that when you drill into them, none of them show the group-id format of the .pom entry, each shows it’s specific project id, not the ${CI_API_V4_URL}/groups(group-id)/-/package/maven form.

Can anyone provide information on where I may be going wrong, or how I can observe the group a dependency is located within?