When attempting to change a grade twice in a row, or by changing a value affecting the sort order and then trying to change another value in the affected row, it leads to the exception mentioned above.

This only happens while pagination is active, a column is sorted via ASC/DESC rules, and a value is modified that leads to the row being on another page.

(We already have MDL-78775 installed, and the user search is working as intended).

Ways to reproduce:

Bugtracker_gradebook-2023-10-27_07.31.45.mp4

1. Create a course with at least 22 students/participants
2. go into grade book setup and add a grade item
3. Scale and setup only need to have enough values to make a sortation with different values between two pages (the standard 100-point scale suffices).
4. Save and go back to the grade book.
5. Give every row a grade so that after sorting and changing a value, that row will be on a different page (e.g., give 20 students a 100 and 20 students a 20)
6. Now only display 20 elements per page.
7. Sort the row by clicking on the header element of the grade item (screen1.jpg)
8. Change the first or second row to a value that would send it back on later pages in this sort order (e.g., 100 changed to 15; that row would be on the last page)
9. After the site reloads, this row is still on display. Try to change any value on it. (Screen2.jpg)
10. The mentioned exception is thrown (Screen3.jpg)

It is not reproducible with displaying all rows.