The auto zero tool seems to be wonky. I have used the tool in my courses for awhile now and it never seems to mark the assignments with a zero until I check and uncheck that option in the course settings. It's a fantastic tool that doesn't seem to work well. For instance, I have one course that had an assignment that was to be marked zero last Saturday at midnight and when I checked today, it still hadn't been marked. Any help with this would be awesome. Thank you!
Could you provide a student enrollment ID and activity ID where it has not auto flunked the student on the activity? I would like to see what may be occurring.
Hello Brian! I was recently taught by Thomas how to use the About/Support/Copy feature, so I am using it here from a gradebook that should have auto zeroed several assignments last night at midnight. If that's not what you need, or won't be helpful, let me know. I can use the admin app to get a user ID but I don't know how to find an activity ID.
I don't know from your example which specific activity ID in that course should have been flunked sooner? Looking at the gradebook now the system has flunked past due students. However, I do see some students where it did not flunk activities and that is because their enrollment start date is in the future in comparison to the activity due date. For example, one has an enrollment start date of 1/26/2021 but the activity has a due date of 1/16/2021.
I am aware of the late coming students and the need to force the system to pick up those zeros with the checking and unchecking the setting. However, every week the gradebook does not flunk after the due date passes. I have tried waiting 12-14 hours after. I have also noticed that students who log in after the due dates passes receive the auto zero. CDLS' Tech Director has a ticket in on this behavior as well. I would be happy to send you whatever you need to investigate this. My next due date is this coming Saturday at midnight.
The behavior encountered as explained in my previous post is expected.
Additionally, the flunk feature is performed by a nightly task. The system will likely not mark student activities flunked at midnight but rather will rather mark it flunked at the time it has processed it. The system task looks for activities in a past due state and then will attempt to flunk them when it runs it's nightly task. That task is run against all customers. Therefore, it can take some time for the task to complete on all activities that need to be flunked. We therefore recommend users wait up to 48 hours for the task to flunk a student submission.
Comments (5)
Hello Chelsea!
Could you provide a student enrollment ID and activity ID where it has not auto flunked the student on the activity? I would like to see what may be occurring.
Hello Brian! I was recently taught by Thomas how to use the About/Support/Copy feature, so I am using it here from a gradebook that should have auto zeroed several assignments last night at midnight. If that's not what you need, or won't be helpful, let me know. I can use the admin app to get a user ID but I don't know how to find an activity ID.
{
"app": "Buzz",
"version": {
"Buzz": "3.0.210",
"Firefox": "83.0",
"xli": "2021.01.12.5362"
},
"user": {
"id": "133125600",
"username": "chelsea.lindsay",
"domainid": "130216026",
"userspace": "coloradodls"
},
"xli": "https://api.agilixbuzz.com",
"url": "https://coloradodls.agilixbuzz.com/teacher/154992722/gradebook/grades",
"params": {
"enrollmentId": "154992722"
},
"date": "2021-01-17T16:25:43.301Z"
}
I don't know from your example which specific activity ID in that course should have been flunked sooner? Looking at the gradebook now the system has flunked past due students. However, I do see some students where it did not flunk activities and that is because their enrollment start date is in the future in comparison to the activity due date. For example, one has an enrollment start date of 1/26/2021 but the activity has a due date of 1/16/2021.
Hello Again!
I am aware of the late coming students and the need to force the system to pick up those zeros with the checking and unchecking the setting. However, every week the gradebook does not flunk after the due date passes. I have tried waiting 12-14 hours after. I have also noticed that students who log in after the due dates passes receive the auto zero. CDLS' Tech Director has a ticket in on this behavior as well. I would be happy to send you whatever you need to investigate this. My next due date is this coming Saturday at midnight.
The behavior encountered as explained in my previous post is expected.
Additionally, the flunk feature is performed by a nightly task. The system will likely not mark student activities flunked at midnight but rather will rather mark it flunked at the time it has processed it. The system task looks for activities in a past due state and then will attempt to flunk them when it runs it's nightly task. That task is run against all customers. Therefore, it can take some time for the task to complete on all activities that need to be flunked. We therefore recommend users wait up to 48 hours for the task to flunk a student submission.