Grade Sync Error - 409 Refusing score with an earlier timestamp

Kaveesha.S.4118
Kaveesha.S.4118 Posts: 3 🔍
edited October 29 in Higher Ed / Postsecondary
Hi D2L Team,

Based on the few escalations reported by customers on the Pearson side, it appears that some users are encountering the following error during the grade sync process.
LmsGradePushException: 409 Conflict: [Requested score timestamp is less than or equal to the timestamp of last score received]\\n\\tat

The examples and details are provided below.
1)
LMS Assignment Id :- "384966ea-cfaa-49a7-88e4-78f96fb68fde"
Assignment title :- "Cell Metabolism Module 02: Cell Metabolism - Cellular Respiration Dynamic Study Module"
Line item URL :- https://brightspace.missouristate.edu/d2l/api/lti/ags/2.0/deployment/f8b54d11-4259-4f1a-adab-82dfef6d3962/orgunit/27924/lineitems/89e0e40a-1f24-4375-a181-84b0b1e8540e
LMS course id :- 27924
System time where the sync occurred:- 2024-07-24T15:36:12.584Z
Payload:-
{
"timestamp": "2024-07-24T15:47:46Z",
"scoreGiven": 5.0,
"scoreMaximum": 5.0,
"comment": "",
"activityProgress": "Completed",
"gradingProgress": "FullyGraded",
"userId": "6a66c00e-2009-40d4-81f6-38f235c6329c_4633"
}

2)
LMS Assignment Id :- "253d6315-a010-48e7-937c-e391a959ed15"
Assignment title :- "Cells and Tissues Module 01: Cells and Tissues - Fluid Compartments Dynamic Study Module"
Line item URL :- https://brightspace.missouristate.edu/d2l/api/lti/ags/2.0/deployment/f8b54d11-4259-4f1a-adab-82dfef6d3962/orgunit/27924/lineitems/ef8cc3de-409c-43b5-8c11-2c34f6079144
LMS course id :- 27924
System time where the sync occurred:- 2024-07-24T15:36:17.650Z
Payload:-
{
"timestamp": "2024-07-24T15:47:51Z",
"scoreGiven": 5.0,
"scoreMaximum": 5.0,
"comment": "",
"activityProgress": "Completed",
"gradingProgress": "FullyGraded",
"userId": "fcb32e9d-903f-4af0-ad57-d2bacda00d28_8942"
}
Note: The timestamp of the payload indicates the time at which the student completed the assignment.

Could you please clarify the reason behind this issue? It appears that the LMS side may not be utilizing the timestamp from the payload parameter we are sending. If that is the case, we would appreciate a detailed explanation regarding this matter.

Thanks!
Tagged:

Answers

  • Chris.S.534
    Chris.S.534 Posts: 378

    Hi Kaveesha.S,

    Best to open a case with the D2L Support team. If this is an issue with a partner integration it may need their collaboration and input. I'd also recommend opening a support case with Pearson to investigate from their end.

    This will be the quickest path for the issue being identified, investigated and resolved.

    Hope that helps!

  • Kaveesha.S.4118
    Kaveesha.S.4118 Posts: 3 🔍

    Hi Chris.S,

    Thank you for your response. We have observed this issue with several integrations and have conducted a thorough investigation on Pearson side. We will proceed by raising a support case for further investigation. Thank you once again for your assistance.