Publish progression status update
Progression
Publish progression status update
Enqueues a progression status update to the FIFO queue. The consumer Lambda writes it to the student’s user metadata in OneRoster. If the studentTimebackId does not exist in OneRoster, the request is accepted but skipped — the response will include skipped: true and a reason field. Served by the progression-status-enqueue Lambda.
POST
Publish progression status update
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Body
application/json
Available options:
gap_analysis_in_progress, gap_analysis_completed, gap_analysis_bypassed, gap_analysis_failed, hf_lesson_picking_in_progress, hf_lesson_picking_completed, hf_lesson_picking_failed, hole_filling_generation_in_progress, hole_filling_generation_completed, hole_filling_generation_pending_onboarding, hole_filling_generation_failed, test_assignment_in_progress, test_assignment_completed, test_exhaustion, test_assignment_failed, placement_prerequisites_not_met, course_assignment_in_progress, course_assignment_completed, course_assignment_pending_onboarding, course_assignment_failed, reassignment_in_progress, reassignment_completed, reassignment_failed, subject_track_completed Learning app the status is about (e.g. freckle, mobymax). Selects app-specific copy — e.g. the Renaissance (~24h SLA) variant of hole_filling_generation_pending_onboarding.