13th of September 2026 (patch release)

This article contains this patch release's bug fixes.

Bug fixes

• Fixed an issue where highlighting text in a table moved values to the wrong columns
  Previously, highlighting text across multiple cells during a digital test could change the table layout and shift values one column to the right. This issue only occurred with tables that were copied from another source and pasted into Ans using the HTML editor. Tables that were created directly in Ans were not affected. Now highlighting text leaves the table layout unchanged, so each value stays in its correct column.
   

• Fixed an issue where attachments would not sync properly
  Previously, when an attachment was removed from a question bank assignment, clicking "Synchronize" on the linked course assignment did not remove the corresponding attachment from the course assignment. The attachment remained in the course assignment, even though it had been removed from the question bank assignment. As a result, the course assignment remained out of sync.

  This has been fixed. Now, when an attachment is removed from a question bank assignment, clicking "Synchronize" on the linked course assignment will now also remove the corresponding attachment from the course assignment. The course assignment will then be in sync with the question bank assignment.
   

• Fixed an issue where API parameters were ignored
  When creating an assignment from a question bank, settings such as "Notepad", "Spellchecker", "View exercises once", "View sections once", and "Show whether closed questions were answered correctly" are normally inherited from the question bank. When using the API, you can override these settings by explicitly providing a value during creation. Previously, these API values could be overwritten during the initial synchronisation with the question bank. Now, API values are preserved. Only settings that are not specified in the API request are inherited from the question bank.

  Subsequent synchronisations continue to work as before. Existing assignments are not affected. If you created assignments from a question bank since 21 July 2026, we recommend checking their settings.
   

• Fixed an issue where students could get stuck on the access code page
  Previously, digital tests that required both an access code and the Schoolyear exam browser would leave students on the access code page after they entered a correct code. Typically, the code is accepted and Ans redirects the students to Schoolyear, but that redirect was being ignored, leaving the student on the access code page. Entering the code again also repeated this cycle, and after ten attempts the access code was temporarily rate limited.

  Entering the access code now opens the Schoolyear exam browser as expected. The same applies to the other checks that run before a digital test starts, such as the assignment password, Safe Exam Browser and ProctorExam.
   

• Fixed an issue where selecting an exercise in a Proctorio-monitored digital test opened a dialog asking the user if they wanted to leave the site
  Previously, when taking a digital test monitored by Proctorio, clicking an exercise in the exercise overview on the left would open a browser dialog asking whether the user wanted to leave the site. If the user confirmed, the page could become unresponsive and the user would be logged out.

  Now, selecting an exercise from the exercise overview no longer displays this dialog, preventing the user from being logged out as a result.
   

• Fixed an issue where comment suggestions showed comments written by other reviewers
  Previously, when adding a comment to a criterion while grading, the 'Previous comments' list suggests comments that were written earlier for that same criterion. Previously, during peer review, self review, and second review, that list showed the comments of every reviewer.

  Now, in peer review, self review, and second review, the suggested comments only shows the comments you wrote yourself. The regular review is unchanged: every comment written for the criterion stays available as a suggestion.
   

• Fixed an issue where Error Carry Forward (ECF) questions would be scored with the original script.
  Previously, when a numeric question using Error Carry Forward (ECF) would fail to create a variable set based on student answers, the question would be scored with the original script instead of the corrected script.

  Now, if any error occurs, it will be retried several times. The question will never be scored with the original script. All affected schools have been contacted, and a detailed impact analysis is ongoing. The post-mortem will be published once the impact analysis is complete.
   

• Fixed an issue where users in the trash were not permanently deleted
  When a user is deleted, they are moved to the trash. If a user is in the trash for longer than 180 days they are permanently deleted. Previously, users with a role in a large number of courses were not permanently deleted after the 180 days and stayed in the trash indefinitely. Now, when a user is deleted and spends 180 days in the trash, they are permanently deleted.
   
• Fixed an issue where a non-numeric student number could be matched to the first user without a student number
  Previously, when a login sent a non-numeric student number, it could be matched to the first user in the institution without a student number. This issue was introduced in our previous release. This issue has been resolved and all affected institutions have been notified.
   

• Fixed an issue where merging two users could fail
  Previously, merging two users could fail with an error, leaving both accounts unchanged. This could happen when both accounts had a stored preference for either the new grading scheme experience or the new homepage. These preferences are saved automatically when a user opens the grading page or homepage, meaning that most active accounts have these preferences stored and could potentially encounter this error.

  Merging now keeps the preferences of the account you merge into and discards any duplicate preferences from the other account. Preferences that are not yet set on the account being kept are still transferred.