This particular scout is a Star rank. None of the advancement data is showing for me.
I am a Key 3, with tons of permissions. I have cleared the cache, tried incognito, etc.
Also, I can see MB data, but no award data.
Thanks for your help!
@ChristopherO_Quinn Please provide the Scout’s member ID number.
(No names, please)
Here is that scout. 136445288
But this is happening for the entire troop
@ChristopherO_Quinn the calculations happen when a rank page is opened - have you opened “Scout” page for the above scout?
When I look at the roster, I see all scouts and their current ranks. Then I click on the individual scout and all rank data disappears as well as awards. I can see MB data, activity logs, Profile data, etc. I’m having the same problem viewing every scout in the troop, except my own scout.
But what if you go all the way to the rank page of a scout?
Your Key 3 Delegate (K3D) role does not look right. It has an expiration date of 6/1/26 while your registered positions have expiration dates of 12/31/26. Were you removed as a K3D?
Do the Key 3 see the same behavior as you?
I am looking at the membership database, your Key 3 Delegate role expired 6/1/26. The expiration should like up with your membership expiration which is 12/31/26. I suggest asking a Key 3 to check my.scouting.org and restore your Key 3 Delegate role if it is not present. If it is present, you will need to contact your Council for assistance because I suspect this is part of your issue.
I would still like to know if your Key 3 (Scoutmaster, Committee Chair or Charter org Rep) sees the same behavior or not.
Look at my.scouting.org - Not SB for postions
Committee chair, SM, Advancement Chair are not having this issue. I’ll get the committee chair to check and restore my Key 3 and. report back.
@ChristopherO_Quinn - it will be 24 hours after being added as a delegate that you can test
Developers have been able to see your behavior. They are investigating.
Committee Chair added me back in as a Key 3 delegate. It’s been over 24 hours. I’ve cleared my cache again. Same issue persists
@ChristopherO_Quinn - as Ed pointed out the dev team spotted something and are investigating.
