AnsweredAssumed Answered

Creating Async Job, rejected because user_id=null

Question asked by Kevin Overall on Jun 27, 2016
Latest reply on Jul 1, 2016 by Kevin Overall

I'm working on an LTI app, and am needing to send grades to Canvas in bulk. I'm using the endpoint:

POST /api/v1/courses/:course_id/assignments/:assignment_id/submissions/update_grades

 

This creates an async job and returns a progress object as expected. The job fails, however, because the submitted user id is null. There, however, does not seem to be a user id parameter for this end point, so I am not sure what to do to debug or how to make sure it is sent. Is this possibly a problem in the authorization process?

 

For reference, here is the progress query result:

while(1);{"id":2926799,"context_id":1876255,"context_type":"Course","user_id":null,"tag":"submissions_update","completion":null,"workflow_state":"failed","created_at":"2016-06-27T18:33:39Z","updated_at":"2016-06-27T18:33:40Z","message":"Couldn't find User(s) with API ids ''","url":~CANVAS URL~}

Outcomes