The May 2026 release delivers enhancements across Workflow Tools, Interview Rooms, and Proctoring, introducing automated evaluator reminders, data-driven candidate shortlisting, improved code execution reliability, and LMS integration improvements.Documentation Index
Fetch the complete documentation index at: https://docs.talview.com/llms.txt
Use this file to discover all available pages before exploring further.
Workflow Tools Enhancements
This month, we introduced enhancements focused on automated evaluator reminders and data-driven candidate shortlisting.🆕 Feature
1️⃣ Workflow Automation: Auto-Remind Evaluators Description: A new automation rule sends scheduled email reminders to evaluators who have not completed their evaluation after a candidate is assigned. What’s New- Automated evaluator reminder emails sent at 24h, 48h, and 72h after candidate assignment if evaluation remains incomplete.
- Applies across all steps: Screening, Assessment, and Interview, within a workflow.
- Dynamic section columns appear in the Assessment step candidate list, one column per section, visible only when the assessment contains multiple sections.
- Supports both numeric scores and categorical scores.
- Section-level filters: range/between and greater/less than for numeric scores; multi-select for categorical scores.
🐞 Bug Fixes
1️⃣ Workflow Tools: Platform Stability- Evaluator reminder emails not triggering; candidate invitation emails failing to send.
- New notifications not appearing without a page refresh.
- Unified assessment steps incorrectly marked as “Completed”; Ivy AI scores displaying as 0.
- Proview index not visible in tabular view; candidate list not loading for Evaluators.
- Time slab display breaking for slots ending at 12:00 AM.
- Sessions scheduled despite failed payments; incorrect redirect from payment gateway.
- Slots not appearing on page refresh; slots incorrectly marked as holidays.
- Reminder emails incorrectly triggering; OTP verification error during offline drive check-in.
- Improved drive slot API load time.
Proctoring Updates
This month, we introduced enhancements focused on improved LMS integration reliability.Integrations: Moodle Native Plugin (V7+)
You can download the latest version of moodle plugin here.⚙️ Enhancements
1️⃣ Sentry Initialization for proctored sessions only Description: Previously, Sentry was initialized for non proctored quizzes as well. Now it is deferred until the check confirming that Proview is explicitly configured and enabled for the quiz in question. For any quiz where Proview proctoring is not active, Sentry will not initialise. Sentry’s role in the plugin is only for error monitoring of proctoring session failures; it is scoped to proctoring-active quiz only. 2️⃣ Enable Password Injection Setting Description: A new Enable Password Injection checkbox is now available in the Proview Proctoring Settings section of the quiz settings page. With this setting enabled, the plugin now handles password injection automatically, removing the need for any manual password sharing outside of Moodle.🐞 Bug Fixes
- API data exposed in browser console API responses were being injected into the browser console during production quiz sessions, potentially exposing session, quiz identifiers to any authenticated user via browser dev tools. This has been resolved - API response payloads are no longer sent to the browser console.
- Quiz password bypass via direct URL access Students could bypass a quiz password by navigating directly to
frame.php, which was unconditionally marking the password as satisfied without validating it. Password validation is now properly enforced through Moodle’s standard access flow before the Proview session can be initiated. - Unenrolled users could access Proview flow Any authenticated Moodle user could access
frame.phpfor any proctored quiz, regardless of course enrolment. The page now enforces course enrolment and quiz access capability checks before initiating the Proview session - unenrolled or unauthorised users are blocked before the proctoring flow begins. - Proview Recordings list capped at 100 sessions The Proview Recordings page was limiting the display to a maximum of 100 sessions with no option to paginate further. Reviewers were unable to access or view recordings beyond the first 100 sessions. This has now been resolved - pagination is supported, allowing reviewers to navigate through all sessions regardless of count.
Interview Rooms Enhancements
This month, we introduced enhancements focused on improved code execution reliability, session playback, and session stability.⚙️ Enhancements
1️⃣ Code Runner: JDoodle Fallback Description: CodeJam code execution now falls back to JDoodle if the primary Judge0 engine is unreachable, ensuring uninterrupted code execution for candidates. 2️⃣ Code Runner: Compiler Version Upgrade Description: The Judge0 code execution environment has been updated to the latest compiler and interpreter versions across all supported languages including GCC, Python, Node.js, and Java. 3️⃣ In-Progress Session Playback Description: Recruiters and coordinators can now view a session recording while it is still in progress, not just after it has ended. 4️⃣ ACS Face Captures Description: In-meeting face capture images now appear correctly in the Verification tab for ACS-based sessions. 5️⃣ ACS Session Timer Description: The in-meeting timer now displays correctly for both interviewer and candidate in ACS sessions. 6️⃣ Screen Recording Quality Description: Screen recording resolution has been increased for V8 sessions, ensuring recordings at high-resolution displays render at the correct quality.🐞 Bug Fixes
- Resolved Insights issues including transcript unavailability and workflow failures during candidate performance save.
- Fixed cross-tenant data issues, partial video in Persistent sessions, and session join errors.
- Resolved screen recording quality, CodeJam UI, and app loading issues.
- Fixed camera preview rendering incorrectly on iOS devices in the pre-join lobby.