This behavior has been resolved and deployed to the production environment as of 1/15/25.
Description
When a user imports an assignment that has no due date, and the user selects the option to shift the dates, submission objects are not created when the import completes. When a single submission object is called, the workflow state is null. This issue also happens when the user selects the option to remove due dates upon import.
This causes many issues, such as: students do not populate in SpeedGrader, students cannot submit assignments, assignments do not show up on the to do list, and students cannot be graded.
Expected Behavior
Submission objects should generate for students
Workaround
-
Edit the due date
-
Run the SubmissionLifecycleManager (aka DueDateCacher)
Steps to Reproduce
Prerequisites: Have two courses with separate course start and end participation dates. The destination course should be published and contain student enrollments.
-
In course A, create an assignment assigned to everyone with no due date, save and publish.
-
In course B, run a course import for all content (Adjust events and due dates → shift dates), and leave the populated dates from course start and end and import. (Or, remove dates can be selected)
-
Call the submissions API for the assignment. Note that the submission objects are not generated.
Additional Info
CLAB-930
Known issues indicate notable behaviors that have been escalated to the Canvas engineering team. Known issues are not a guarantee for an immediate resolution. This document is for informational purposes only and does not replace the Support process. If you are encountering the behavior outlined in this document, please ensure you have submitted a Support case (per your institution's escalation process) so Canvas Support can adequately gauge the overall customer impact and prioritize appropriately.
