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
A production incident and subsequent local testing revealed that when an assignment's "Points Possible" value is changed, the "graded_at" value of Canvas submissions are updated. This results in the scores being pulled by the application's process again, resulting in duplicates, or scores from before the integration was installed being pulled for the first time.
Can we do anything to mitigate this? "submitted_at" values may not change, but those values are null if the scores are entered manually by the instructor without the student actually submitting some material or content. We could incorporate data from the assigment/x API endpoint, but that may involve a significant refactor.
This is under discussion; we may end up just documenting this issue and ensure users understand the impact of changing "Points Possible" value and plan accordingly (i.e. remove old submissions, double-check point ranges before an integration is in place, etc.). Duplicates in and of themselves may not be problematic to the SA system. If we don't take action via a code change, this issue should be labeled as wontfix and closed.
The text was updated successfully, but these errors were encountered:
A production incident and subsequent local testing revealed that when an assignment's "Points Possible" value is changed, the "graded_at" value of Canvas submissions are updated. This results in the scores being pulled by the application's process again, resulting in duplicates, or scores from before the integration was installed being pulled for the first time.
Can we do anything to mitigate this? "submitted_at" values may not change, but those values are
null
if the scores are entered manually by the instructor without the student actually submitting some material or content. We could incorporate data from theassigment/x
API endpoint, but that may involve a significant refactor.This is under discussion; we may end up just documenting this issue and ensure users understand the impact of changing "Points Possible" value and plan accordingly (i.e. remove old submissions, double-check point ranges before an integration is in place, etc.). Duplicates in and of themselves may not be problematic to the SA system. If we don't take action via a code change, this issue should be labeled as
wontfix
and closed.The text was updated successfully, but these errors were encountered: