Bug: Error Scoutbook legacy_we encountered an error trying to process your request

Good afternoon,

Last week I received error messages about permissions, after being assigned a Unit Admin role in Legacy Scoutbook as recommended here, I noticed the message error no longer appears, however, no actions work when I click on any of the scouts from 10G or 10B.

I’m one of three ASMs, and I’m the only one having this issue.

Reference MID: ASM/Troop admin and MBC MID: 141298146

In Legacy Scoutbook, I go to Roster, either 10G or 10B click any Scout, click on Scout Merit Badges, click on any of the MBs and this message appear: Error Scoutbook legacy_we encountered an error trying to process your request.

Troubleshooting attempted: Incognito browser, hard refresh, clear cache and none of these resolved the issue and same thing happens in Chrome, Edge, or iPhone mobile.

Here all the MIDs:

All Scouts MIDs 10G

All Scouts MIDs 10B_more

All Scouts MIDs 10B

Is there anything else I can do on my end to have this resolved before our first meeting this Friday? Thanks in advance!

@P.L

Thank you for the details. This is a known issue in Legacy Scoutbook. Use Scoutbook Plus for MBs and Scouts you are not counseling.

For MBs and Scouts you are counseling, you can use the MBC section of My Dashboard in Legacy Scoutbook.

Thank you for the guidance. I tried using both Scoutbook Plus and Legacy Scoutbook as suggested, but unfortunately still not able to take any actions. When I click into the roster (whether for Scouts I am counseling or others), no options are available.

@P.L- are you using this menu-

1 Like

Thanks for the tip! This is the only method that worked, and I was at least able to enter information for the Scouts I counsel. I appreciate the help. Do you know if the developers have provided an estimated date for resolving the bug that’s affecting some ASMs?

@P.L- I would have no idea.. I am just a volunteer like you

Thank you very much for your response. Hopefully we’ll have an update soon, as I’ve noticed several other posts related to this bug as well. Thanks for your support.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.