...
Instead of scanning the entire course, the recheck functionality scans only the blocks identified during the previous scan. However, implementing this feature has been deemed too complex for the initial release of Course Optimizer. For more details, refer to the original planning document.
NEW Based on the helpful comments, I have added three possibilities as future enhancements:
Automatically Run & Warn Authors: extend this check to run in the background once for your course and give you a heads up via email or course outline page message. When / how to do this might be tricky to define since course publishing workflows vary greatly. As an example, perhaps only run if it wasn’t run manually and if there are published unit pages in your course with the start date N weeks away? This could help catch issues before a course goes live.
In-Context Checks for Text + Problem Blocks: how much cost / effort it might be to run this course optimizer for just a singular block. If it was quick to run the optimizer just in time after draft publish or draft save of any text / video components, you could show a unit page or block level message warning for any detected broken links soon after authoring.
Find a way to enable authors to fix the link from the checker: rather than taking them away to the block - Axim have some related designs mocked up for the “sync feature” for library content in courses (see story 11). There’s a modal that lets the authors scroll through a list of components that have updates available, and accept/deny the changes from within the same modal. I can see something similar here, with an option to edit the links directly in the modal.
Additional Information
Competitive research (Canvas)
...