The table below lists resolved issues that require specific post-upgrade actions by On-Prem customers. If you have encountered any of the issues listed, please follow the instructions provided in the Actions to Take column after applying the fix.
This list is reviewed and updated with each release and patch release as needed. Action items will remain listed for up to six months following the release date of the version containing the fix, after which they will be removed from subsequent release notes.
Internal Reference ID | Fix Version | Release Date | Category | Issue Description | Action Item |
|---|---|---|---|---|---|
PROC-8889 | 2024.11.2.2024 | 6/29/26 | Imports | Fixed an issue where new on-prem MAPI projects were populating email address fields (From/To/CC/BCC) and the Participants table with internal Exchange X500 addresses instead of standard SMTP addresses. | Any affected values would be corrected at the end of the next import job. If all data has been ingested, a dummy job could be created with a single text file, for example, that would retroactively resolve any existing values. |
PROC-8867 | 2024.11.2.2024 | 6/29/26 | Exports | Fixed a bug where importing a global export template JSON file would fail with an error if the template contained placeholder settings. | Re-attempt template import. |
PROC-8839 | 2024.11.2.2024 | 6/29/26 | Version Upgrades | Fixed an issue when upgrading existing projects to version 2024.11.2.1927. Dupe Exchange/Outlook attachments were automatically populated with an Evidence ID inherited from the master document during deduplication propagation. This caused custom scripts to skip over the fields and leave them without a proper Evidence ID assignment. Processing Summary Reports were also affected and showed duplicate EO attachments under the master document's Evidence ID. | Please reach out to support, who can run a script that can correct your data |
PROC-8765 | 2024.11.2.1982 | 6/15/26 | Import | Resolved an issue where imports were becoming stuck during the Dupe Propagation stage. The import process now completes without generating the previously encountered error messages, allowing customers to successfully import files into Discovery Manager. | If error has been encountered reprocessing using the "retry errored tasks" checkbox on the resume screen should allow for resubmitting and retry of these tasks to complete successfully. |
PROC-8760 | 2024.11.2.1982 | 6/15/26 | Project Management | Fixed an issue where project creation failed when the instance prefix was set to "TVDB". The naming logic has been updated to ensure consistent database name generation, allowing project creation to complete successfully. | Updated solution should now allow project creation to complete. |
PROC-8733 | 2024.11.2.1982 | 6/15/26 | Export | Fixed an issue where Australian Protocols exports failed when MASTERDATE was selected as the primary field in the Sort Order configuration. | Re-attempt export. |
PROC-8732 | 2024.11.2.1982 | 6/15/26 | Export | Resolved an issue where exports configured to sort by IMPORTPATH were instead being returned in an inconsistent order, often following FILEID/TV Family ID sequencing. The export sorting logic has been corrected to ensure that files are ordered according to the selected IMPORTPATH sort option, providing expected export results. | Re-attempt export. |