Deleting Repos, Collect Scores Failure

[schrum2]

When setting up my classroom, I checked out every repo and solved it myself to verify the autograders work. Now the semester is about to start. I often like to show students the process of checking out a fresh repo and point out some important information in the original, unmodified code, so I did what I used to do in GitHub Classroom: I deleted my previous repos. This seems to work fine, and now when I click the assignment link, Classroom50 offers to let me accept the assignment anew rather than go to my old repo.

So far, so good.

However, ever since I mass deleted repos, I get an email from Classroom50 every night around 11:30pm titled "Run failed: Collect Scores - main" that says "Collect Scores: All jobs have failed". Also, on top of this, I've begun inviting students to my class. I also tried deleting some information about my previous submissions in the classroom50 repo in hopes of stopping the grading attempts, which might have partially worked. However, at this point, so many things have changed that I'm not sure what the cause is, or if multiple issues are related. I just know that when I "View workflow run" and look at "Collect scores" I see various types of errors and warnings. Here are some examples, with student account names replaced with phony ones for anonymity:

Warning: su-schrum-classes/computer-organization-fall-2026-cop1-fastmultiplication-schrum2: could not grant 'classroom50-computer-organization-fall-2026-ta' pull: HTTP 404 (Not Found); skipping
Warning: su-schrum-classes/computer-organization-fall-2026-cop1-fastmultiplication-student: could not grant 'classroom50-computer-organization-fall-2026-ta' pull: HTTP 404 (Not Found); skipping
...
Warning: su-schrum-classes/computer-organization-fall-2026-cop2-binarysearch-schrum2: could not grant 'classroom50-computer-organization-fall-2026-ta' pull: HTTP 404 (Not Found); skipping
Warning: su-schrum-classes/computer-organization-fall-2026-cop2-binarysearch-student: could not grant 'classroom50-computer-organization-fall-2026-ta' pull: HTTP 404 (Not Found); skipping
...
and so on for every assignment and every student in the class computer-organization-fall-2026
...
Error: computer-organization-fall-2026: staff-team access grant failed with HTTP 403 (Forbidden) — grant staff teams repo access needs a fine-grained PAT with Repository -> Administration: Read and write; run gh teacher rotate-service-token su-schrum-classes. Score collection continues; TAs may not see student repos until this is fixed.
...
Warning: su-schrum-classes/programming-languages-fall-2026-crashcourse-java-student: could not grant 'classroom50-programming-languages-fall-2026-ta' pull: HTTP 404 (Not Found); skipping
Error: programming-languages-fall-2026: staff-team access grant failed with HTTP 403 (Forbidden) — grant staff teams repo access needs a fine-grained PAT with Repository -> Administration: Read and write; run gh teacher rotate-service-token su-schrum-classes. Score collection continues; TAs may not see student repos until this is fixed.
Warning: programming-languages-fall-2026: collected 0 submissions across 25 assignment(s). If you expected submissions, either the classroom team has no members yet, or the CLASSROOM50_SERVICE_TOKEN lacks read access to the student repos (a fine-grained PAT returns 404 for repos outside its scope, which is indistinguishable from "not submitted"). Re-scope it to all org repos: gh teacher rotate-service-token su-schrum-classes
Error: collect: 2 classroom(s) had a failure (staff-team grant and/or scores write): computer-organization-fall-2026, programming-languages-fall-2026. Score collection ran for every classroom; a grant-only failure means TAs may not yet have access.

Some clarifications about the errors/warnings above:

• All repos for computer organization give warnings, but only some for programming languages do
• There are no TAs in the class.
• For some reason, the roster.csv for each class lists my role as "ta". I tried changing it to "teacher" but something changed it back. The commit that changed it back was named "[Classroom 50] Sync 0 members into roster: programming-languages-fall-2026"

Question: Does Classroom50 always try to regrade everything every night even if there have been no changes in repo status?

[rongxin-liu]

Classroom 50 currently creates four teams for each classroom:

1. classroom50-<classroom>
2. classroom50-<classroom>-ta
3. classroom50-<classroom>-hta
4. classroom50-<classroom>-teacher

If you are still a member of teams 1 through 3, please remove yourself from them.

For the score collection script, we currently configure it to run nightly by default. However, that is probably not the desired behavior, so we may change it to run on demand instead. Classroom 50 itself does not trigger nightly score collection; the nightly runs are caused by a cron job defined in the workflow.

As for the warnings you are seeing, they are most likely caused by assignment repositories that were not created. As a result, the script failed when trying to grant the -ta and -hta teams access to those repositories.

Currently, we create the TA and head TA teams regardless of whether a course actually has TAs or head TAs. There may be room for improvement by creating those teams only when needed. For now, we want to keep things simple by always pre-creating the staff teams and granting them permissions, even if they have zero members.

Regarding the service token error, have you tried setting a new token to see whether the same 403 errors occur again?

[schrum2]

I want to make sure I don't accidentally prevent myself from accessing the class content, so I'm proceeding cautiously. I'm not seeing the 4 teams you mention. I'm seeing 3 teams per class:

classroom50-
classroom50--ta
classroom50--instructor

I'm a member of all 3 of these.

There is no:
classroom50--teacher

I can certainly remove myself from these two:
classroom50-
classroom50--ta

but the *-teacher team doesn't even exist, and I'm worried that maybe *-instructor is ignored? Will I maintain access to the class? Should I make the *-teacher team, or would it just be ignored by my old version of the classroom?

I guess a lot has changed in the short time since I initially set up the class, but I don't want to rebuild it from scratch after all the work I did setting up the assignments (and students have started joining the class, so I don't want to tear it down and make a new one).

I'll report about the service token issue later.

[rongxin-liu]

The -instructor team is no longer used, but you can rename it to -teacher. A lot has changed over the past two or three weeks, and you may have missed the migration window. We usually try to avoid breaking changes, but in this case, we needed to make these updates early, before the fall semester.

We can see if we can ship an update that would self-heal some of the classrooms that were created during the early iterations of the app.

[schrum2]

Ok, so I renamed the group. Also, last time I logged in I was offered the chance to migrate my old settings to the newer configuration, so I ran that too. I also updated my service token. Last night, I still got the same email, though the specific errors and warnings were slightly different. It was still giving me a lot of warnings like this:

Warning: su-schrum-classes/computer-organization-fall-2026-cop1-fastmultiplication-student: could not grant 'classroom50-computer-organization-fall-2026-ta' pull: HTTP 404 (Not Found); skipping

This is repeated for every assignment and every student in the class, then there is this:

Warning: computer-organization-fall-2026: could not read staff team 'classroom50-computer-organization-fall-2026-instructor' (instructor) members: HTTP 404 (Not Found); skipping that team's members for collection.

I renamed the -instructor team to -teacher as you suggested, but there must still be a setting somewhere that is telling the code to look for that old team. I also see this:

Warning: computer-organization-fall-2026: collected 0 submissions across 8 assignment(s). If you expected submissions, either the classroom team has no members yet, or the CLASSROOM50_SERVICE_TOKEN lacks read access to the student repos (a fine-grained PAT returns 404 for repos outside its scope, which is indistinguishable from "not submitted"). Re-scope it to all org repos: gh teacher rotate-service-token su-schrum-classes

This simply seems to be the expected behavior, but I wanted to make sure. The class is just starting, but no one has actually submitted any assignments yet, which I suppose is the reason for this warning.

Those were all the warnings for the computer organization class, and I got similar warnings for my programming languages class, but I also actually got an error for that one:

Error: programming-languages-fall-2026: staff-team access grant failed with HTTP 403 (Forbidden) — grant staff teams repo access needs a fine-grained PAT with Repository -> Administration: Read and write; run `gh teacher rotate-service-token su-schrum-classes`. Score collection continues; TAs may not see student repos until this is fixed.

I'm not too worried about this because I don't have any TAs, but I do find it odd that I'm getting a different error. Then finally, this last error seems to just be a follow up on the other one:

Error: collect: 1 classroom(s) had a failure (staff-team grant and/or scores write): programming-languages-fall-2026. Score collection ran for every classroom; a grant-only failure means TAs may not yet have access.

Ultimately, none of these errors or warnings seem serious. However, I'm wondering if I'm doomed to receive these emails every night. Am I only receiving them because there are errors and warnings? Or would I receive a nightly email even if everything works? I don't think my assignments need a nightly re-grade. I was just expecting them to be graded whenever a student made a new submission, which is what they are used to from GitHub Classroom. The system certainly doesn't need to be attempting to grade assignments that students have not submitted yet.

[rongxin-liu]

We already turned off the nightly collection, so if you update the workflow files when prompted, your collect score workflow will no longer run on a scheduled cadence.

[rongxin-liu]

If the error message still mentioned instructor, then it suggests that your workflow files are quite outdated, and our app should prompt you to update them. The "instructor" keyword was removed from the codebase about three weeks ago.