You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is some kind of bug in the STAR bundle that prevents all three subjects from running simultaneously. When running more than one subject and sending the results using Lightbeam, a subset of studentAssessments records (about one-fifth) will fail with this error:
The value supplied for the related `studentassessmentstudentobjectiveassessment` resource does not exist.
This is caused by a handful of objectiveAssessments records failing with the following:
409: The value supplied for the related `objectiveassessment` resource does not exist.
Again, this only happens when running multiple subjects at the same time. My theory is that multiple subjects share several objective assessments and set the same unique identifier for each. Then, the latest-version of the objective assessment matches only one subject, causing the other subject to fail. We may want to include the top-level assessment identifier in the objective assessment identifier or MD5 hash.
The text was updated successfully, but these errors were encountered:
There is some kind of bug in the STAR bundle that prevents all three subjects from running simultaneously. When running more than one subject and sending the results using Lightbeam, a subset of
studentAssessments
records (about one-fifth) will fail with this error:This is caused by a handful of
objectiveAssessments
records failing with the following:Again, this only happens when running multiple subjects at the same time. My theory is that multiple subjects share several objective assessments and set the same unique identifier for each. Then, the latest-version of the objective assessment matches only one subject, causing the other subject to fail. We may want to include the top-level assessment identifier in the objective assessment identifier or MD5 hash.
The text was updated successfully, but these errors were encountered: