openedx/openedx-platform

POST /api/instructor/v2/courses/<key>/reports/problem_responses/generate for a problem whose section was published within the last publish-task delay (~30 s on Tutor) answers 200, and the task then raises UsageKeyNotInBlockStructure. The report reads the collected block structure, which the delayed publish task rebuilds. There is no task id returned for this task to read the failure from, and instructor_tasks lists only running tasks, so it is simply empty. To the instructor the report just never appears, with no error anywhere in the UI. Expected: validate the location against the collected structure in the view and answer 400 with a clear message, or have the task fall back to the modulestore. Returning a task id as other tasks do would also let a client surface the failure.

Copying a block to the clipboard intermittently answers 500 {"error": "The Studio servers encountered an error"}. The CMS log shows: django.db.utils.OperationalError: (1213, 'Deadlock found when trying to get lock; try restarting transaction') from content_staging/views.py:136 → api.py:189 save_xblock_to_user_clipboard → models.py:176 UserClipboard.save, on the update_or_create of the row. Load-dependent and somewhat rare: four deadlocks across an E2E CI run. Each concurrent copy was made by a different user, so the contention is not two writers on one clipboard row; the surrounding transaction takes locks in an order another concurrent CMS write can cross. Expected: retry the deadlock, as the platform does elsewhere for 1213, or narrow the transaction.

Where: DELETE /api/libraries/v2/<lib>/ (content_libraries/rest_api/libraries.py delete → api/libraries.py delete_library) on Tutor main (edx-platform master e2e8edf73f). What happens: a library that only ever held components deletes cleanly (200 {}, then 404). A library that has had a unit/subsection/section, or a publish with side effects, answers 500 {"error": "The Studio servers encountered an error"}; the CMS log shows django.db.models.deletion.RestrictedError: Cannot delete some instances of model 'LearningPackage' because they are referenced through restricted foreign keys: 'EntityListRow.entity', 'DraftSideEffect.cause', 'DraftSideEffect.effect', 'PublishSideEffect.cause', 'PublishSideEffect.effect'. Expected: Probably a descriptive 400 error

GET /api/course_home/v1/navigation/<course key> answers HTTP 500 with the LMS error page for a window after a publish. The log shows LearningContext.DoesNotExist then CourseOutlineData.DoesNotExist: No CourseOutlineData for <course key>. The learning_sequences outline the view depends on is written by the CMS worker on the publish signal. On the measured run that task landed 33 s after the publish, because the same queue was carrying thousands of per-block content.search.tasks.upsert_xblock_index_doc tasks, each taking around 21 s. Until it lands the learner's course home cannot be built at all, while the neighbouring course_home/v1/outline view and the Blocks API both answer 200 for the same state. Expected: treat a missing CourseOutlineData the way the outline view does, falling back to the unfiltered blocks or answering an empty model, rather than a 500. Environment: Tutor main, 2026-09-11, with ENABLE_COURSEWARE_INDEX = True and Meilisearch-backed Studio content search on.

GET /api/courses/v1/blocks/?course_id=<key>&username=<learner>&depth=all answers HTTP 500 with the LMS error page when the learner is enrolled in a course whose start date has not passed. The log shows KeyError: 'self_paced' then AttributeError: Field self_paced does not exist, raised from the course-blocks transformers reading the course block's fields. Every neighbouring learner endpoint handles the same state cleanly: course_home/course_metadata returns course_access: {has_access: false, error_code: "course_not_started"} course_home/v1/outline and /navigation answer 403 {"detail": "Course has not started"} courseware/sequence/<id> answers 404 the same Blocks API call as global staff answers 200 Moving the course start into the past makes the learner's call answer 200. Expected: answer the not-started case the way the course-home APIs do, with a 403 carrying the access error, rather than reaching the transformers with a course whose fields were never collected.