While attempting to enter an advancement for a scout in my den (ID 14341888), I was presented with a bad request error. I have attached a screenshot to show the error message I received. This error is limited to this single scout (so far). I have successfully entered the same advancement for other scouts in my den during the same session. Any assistance in resolving this would be greatly appreciated.
This is a known issue. The developers are working on a fix. Watch Scoutbook - Scoutbook Plus Change Log - Scouting Forums for an announcement.
did some one try to implement a change to force us to do the requirements in order. I have gotten the same error on one of my scouts and the only difference from that scout and another is that requirement one was done for one and not the other.
No, there is no requirement to do requirements in order. The developers are aware of this bug and are working on a fix. What the Scoutbook - Scoutbook Plus Change Log - Scouting Forums for an announcement.
@edavignon & @RobertWillhelm - for what it’s worth, my experience is the same as Robert’s. The error occurs when requirement 1 was not completed. Regardless, thanks for the quick reply Ed. It’s nice to at least know this is being worked.
We are getting the same issue to. for what is worth I can not ping coreapipd.netbsa.org. Looks like no dns entry for the subdomain.
I am only having the issue with My Family Adventure.
Can we get the BSA Member ID (no names) of the Scout(s) you are having trouble with? Did you use Quick Entry or try to manually update My Family Adventure? What is the error message?
@edavignon I’m having the same issue with one off my Cubs on King of the Jungle, ID number 140941764. I’ve tried both manual entry, quick entry, and the app. I’m only checking off the first three requirements as she still needs to complete the fourth requirement. Thanks for the help!
I am having the same issue when using the Quick Entry for the required “Footsteps” Belt Loop Award for Wolf Scouts, BUT it affects only my Wolf Scouts that are NOT NEW this year. Wolf Scouts that joined this year, I had no problem entering using Quick Entry in Scoutbook Plus. This is Pack 7, Atlantic District, Coastal Georgia Council, Cubmaster Jim Knauff.
Just discovered that we have the exact same issue as JamesKnauff. Put in Footsteps for one Scout who is new this year, worked just fine. Tried to put it in for Scouts who are NOT new, and get the error mentioned above.
Having this issue as well for entire den for Duty to God in Arrow of Light. Please advise.
Marnie
Den 19
Pack 114
Monon District
Crossroads of America Council
I am having the same error across multiple dens.
Tiger Bites
Wolf Footsteps
Pack 13
Chief Cornplanter Council
I have the same error for one of my scouts across multiple achievements. It does not seem to matter which requirement it is for (1st vs 3rd) and is happening on pretty much every achievement we tried. On one achievement, he had finished the belt loop, so I just skipped the requirements and put the final completion date, which worked fine.
Please post the BSA Member IDs (no names)
His member ID is 13830769
On another similar thread, one of the posters discovered that there error was (at least in part) derived from having some of their scouts on the current (2024) version of the adventures and some on the prior/old version. The break between your new and your previously-registered scouts suggests this might be a similar issue.
Can y’all take a look at the version of both the rank and of the individual adventures for each of your scouts who aren’t working? If the rank looks OK, try the individual adventures that are failing. If all of those look OK, try toggling the rank version from 2024 to 2016 , then back to see if that “forces” the rank and the adventures onto the current version.
I’m not suggesting this is the “right” way this should be working. Rather, I’m trying to extrapolate (from what I we see as users) a work-around that might be faster than waiting for the developers to identify, patch, test and release the fix. If it doesn’t solve the issue, at least that’s more data for the developers to use to diagnose the underlying problem.
Developers think this is fixed - can you please test for these 400 errors
I was able to update my scout tonight with no problem. Thanks!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
