Welcome! This forum has a treasure trove of great info – Scouters helping Scouters! Just a heads up, though - all content, information, and opinions shared on this forum are those of the author, not the BSA.
BOY SCOUTS OF AMERICA

Scouting Forums

Report could not be loaded. Please try again

Attempting to generate the advancements report (to try to investigate why it is missing a lot of advancements!) I am getting “Report could not be loaded. Please try again” after hitting “Generate Report.”

After returning to the Internet Advancement tab I get a pop-up message “Unable to find the user for the given id 2721828”

2 Likes

I have passed this on to the developers.

1 Like

@SeanYeomans

The developers would like the URL of for the report generating the error.

I am also getting this same message.

Please post the URL that is generating this message.

Is this what you are looking for?

https://advancements.scouting.org/roster

https://advancements.scouting.org/reports/output

What we need is the URL from the page that has the error.

https://advancements.scouting.org/reports/output

This is the URL. This is what happens… I recorded some advancements and I see the little notification up top that says needs purchasing. When I go in to that I click generate report. When I do this I get to the page for the URL I just posted. THis is a blank page that says the report could not be generated please try again.

When close that window and go back to the report preview where it says what needs to be purchased that error message pops up and then goes away.

I willl go back into it and try to get screen grabs for it.

screen grab 1.pdf (25.3 KB) screen grab 2.pdf (103.1 KB)

That is exactly what I’m experiencing whether I do it from the “purchase” at the top of the screen or the “run report” at the top of the roster.

Any further updates on this? It’s still not working.

Not yet. The developers are looking into an API issue that could be causing this and other problems.

1 Like

It’s still not working. Do we have any estimate on when this will be fixed?

I have passed this to the developers. Thanks for the update.