This sounds like a known glitch that we’ve been trying to track down, but we don’t have a lot of data to go on so it’s been difficult to pinpoint. If those of you who are having the problem could send me a message through our contact form with details on the resource title, student it’s assigned to, and which division the problem occurs on, that would be very helpful.
As suzukimom mentioned, reloading the page should clear up the problem when it happens. And as we keep getting reports, we’ll continue to try and figure out what’s going on.