Use “Grade DeepTutor answers” in Recued. Scheduled class batch. It uses the connections and settings you choose when you run it.
Grade DeepTutor answers
Use “Grade DeepTutor answers” in Recued. Scheduled class batch. It uses the connections and settings you choose when you run it.
Complete workflow
Use DeepTutor Records in Recued for education, tutoring, student and assignment record-keeping. It stores students, assessments, answers, artifacts and scorecards, and includes 9 ready-to-run workflows that enrol students, send assessments, capture answers and grade them. It needs the DeepTutor pack for question generation. It runs locally on your machine. Actions that change data use Recued's approval controls.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Enroll free DeepTutor student” in Recued. Exact-form enrollment template for a free class.
Use “Register paid DeepTutor student” in Recued. It turns one complete Seller order into a class roster record.
Use “Send DeepTutor assignment or exam” in Recued. Scheduled class dish. It uses the connections and settings you choose when you run it.
Use “Capture DeepTutor answer” in Recued. It runs on its own when a student emails their answers back, and files that reply as a pending answer so the grading workflow can score it on the next run.
Use “List DeepTutor assignments and exams” in Recued. It provides a read-only class index over the DeepTutor pack's own assessment records.
Show all 9 recipes
Use “View DeepTutor assessment” in Recued. It provides a read-only exact detail for one DeepTutor assignment or exam.
Use “View DeepTutor scorecards” in Recued. Lists the derived assignment and exam scorecards the DeepTutor pack keeps in its own records. Supply one Seller customer id for that student's rows, or leave it blank for the owner-wide scorecard list.
Use “Require DeepTutor records runtime” in Recued. It confirms this server can store the class records the other DeepTutor workflows depend on, and stops with a clear message when it cannot.
Scheduled grading
Save one clone per Seller tier/class and assessment namespace. The answer batch is clamped to 1..10, but assessment question_count itself has no authored ceiling. Before any model call, each compact answer manifest drives exact file reads: Recued decodes, hashes, parses, and identity-checks both the student submission and its assessment artifact. One foreach op-step grades each verified multi-question submission as a whole.
The grader must answer exactly CORRECT|feedback, PARTIAL|feedback, or INCORRECT|feedback; those map to 100, 50, and 0. Feedback is bounded to 1,000 characters; it is stored in the answer record’s own long-text slot, not inline in a key-value envelope. Malformed output becomes needs_review with a null score and is not emailed. DeepTutor chat is not used for grading because its v1.5.5 general chat capability mounts internal tools.
Crash posture is unchanged in shape and now rides the record’s own protected revision: pending -> graded_pending_delivery before mail -> graded_delivered after mail, each update asserting the revision it read. Scorecards are recomputed only from graded_delivered answers, one scorecard record per (student, namespace). Records are pack-owned (D-221), so every row also carries the pack version it conforms to.
What the run report counts
Every batched step reports what LANDED, not what was attempted. A rejected write inside a batch is a per-item failure — the run itself still reports success — so Scorecards written counts only the writes the store accepted, Scorecard write failures counts the rest, and the scorecard table lists the rows that actually persisted. When the two disagree, the difference is real: the run did less than it set out to do.
Because this dish runs on a schedule, nobody is reading that card. Notify me when a scheduled run fails partway (on by default) sends one notification when a feedback email or a scorecard write is rejected. Nothing is lost either way — answers whose feedback failed stay at revision 1 and are retried next run, and rejected scorecards are recomputed from delivered rows next run — but without the notification the shortfall is invisible until someone opens the dish.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
class key
setting
=
[object Object]
batch limit
setting
=
5
assessment kind
setting
=
assignment
notify channels
setting
=
in_app
notify on failure
setting
=
true
sender mail instance
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.