Engineers are currently investigating the issue.
Description
In courses with a large number of students, discussion mentions start acting erratically.
-
When you type @, the users take a moment to load, and only 20 users are loaded.
-
If you start typing a name to narrow down the results then any matches in the 20 users already loaded will briefly show in the list before the list closes without any indication that additional users are being loaded - if no users in the current list match what you are typing then the list just closes without any indication that more users are being loaded. Once the new graphQL request returns, the list of mentionable users matching the search term re-appears.
-
If there are no users which match the entered name then the list of mentionable users just never re-appears and there is no indication that no users match the name you typed.
-
If you start typing a name, pause briefly for enough time to allow the graphQL request to be made but not long enough for it to return, then continue typing a name the original graphQL request will be canceled without a new request with the currently entered name being made so even if there are matches in the course for the name you entered they will not display. You have to delete all the characters until you get back to just the @ sign and wait for the original 20 users to display then start typing again, delete all the characters in the mention including the @, or reload the page to get the search to work again.
Expected Behavior
Mentions should function in courses with a larger number of students.
Workaround
No workaround exists at this time.
Steps to Reproduce
Prerequisites: Published course with a large number (150+) of active students
-
Create a discussion.
-
Act as the teacher or a student.
-
Try mentioning other users in a reply to the discussion.
Additional Info
VICE-5437
Known issues indicate notable behaviors that have been escalated to the Canvas engineering team. Known issues are not a guarantee for an immediate resolution. This document is for informational purposes only and does not replace the Support process. If you are encountering the behavior outlined in this document, please ensure you have submitted a Support case (per your institution's escalation process) so Canvas Support can adequately gauge the overall customer impact and prioritize appropriately.
