Known issues
This topic covers the 2026.0 release. For an overview of release updates, see Release updates.
This release of WorkZone contains the following known issues at the time of release, as well as any known mitigation or workarounds.
WorkZone landing page
SSO login failure
If you log via Single Sign-on (SSO) on the WorkZone landing page, you may encounter a "WorkZone failed to load" error and you cannot access the page.
Workaround: To bypass the landing page, navigate directly to /app/client or /app/configurator.
WorkZone Client
The Share > In mail menu for cases and document is not visible, although WorkZone for Office client is installed
This might happen, if you have manually removed the custom font installed by WorkZone for Office.
Workaround: Reinstall the WorkZone for Office client on your local machine and do not remove the custom font.
Microsoft Excel crashes on Microsoft Office 2016 if opened from WorkZone Client
This issue is only relevant for customers with extended Office 2016 support.
Excel crashes on Office 2016 when it is opened from WorkZone Client. This is not a WorkZone issue. To solve the issue, install all Microsoft Office updates. For information about updating Office, see the Microsoft article Update Office with Microsoft Update.
Some AI entities for redaction might provide incorrect suggestions
For AI suggested redactions (available under Advanced PDF > Redaction pane > Search using AI), the following entities might work incorrectly:
- Legal code section: The resulting suggestions are not exact. We recommend not to use this entity in the 2023.3 version.
- Dates: Sometimes not all digits within the dates are found and/or suggested for redaction.
- Phone numbers: Sometimes the resulting suggestions include other numbers than the phone numbers.
Reports are saved as regular PDF files after PDF/UA validation
PDF/UA validation often fails for standard and custom reports, as well as case documents selected for print to a PDF file. These reports are still available as regular PDF files.
WorkZone 365
Outlook: If no default party role is defined for the Primary party field in the Create new case dialog, it is not possible to change the role later in WZC
If the Create new case dialog has been configured to show the Primary party field, but no default party role has been selected for the primary parties that are added via Outlook, the primary parties will be saved to WorkZone without a party role, and it is not possible to change it.
Workaround: A user with the CONFIGADM access code must select a default party role to be applied to primary parties that are added via the Create new case dialog in Outlook. To select a default party role, click Configure in the Create new case dialog, go to the Primary party field, and click the Advanced settings icon, where you can select your party role to be applied. When you have done this, go to the relevant case in WorkZone Client and, in the Primary party field, select a new party from the dropdown list. When you change the primary party, the default party role is automatically updated, and you can change it back to the initial primary party.
Multi-select functionality (for saving multiple emails to WorkZone) does not work in Outlook
Workaround: Clear the Office cache, as described in this Microsoft article.
When DateTime or Date custom fields are set to be mandatory, 'Date/Time is required' warning is displayed immediately after configuring the custom field
Workaround: If you enter an invalid date format, the last valid date from this field will be automatically inserted instead. If you enter an invalid time format, the last inserted valid time will be automatically inserted instead.
Add-in warning after trying to add new fields during case creation in WorkZone 365 (only for Office 2019 with Internet Explorer 11)
On Office 2019 with Internet Explorer 11, when configuring a new case dialog from WorkZone 365, a warning that "This add-in is not responding" is shown after you add a few fields.
Workaround: Close the warning and continue to add the needed fields.
OAuth authorization for Outlook Online fails in Safari browser
For purposes of security and privacy, Safari 12 includes the Intelligent Tracking Prevention (ITP) 2.0, which does not allow the browser to set any 3rd party cookies and treats the cookies set by Identity Providers as 3rd party cookies.
Workaround: Disable the ITP setting (go to Preferences > Privacy tab, and deselect the Prevent cross-site tracking option under Website tracking).
Mail categories for emails saved to WorkZone are not supported for Microsoft Exchange 2019
Mail categories for emails saved to WorkZone are only supported with Microsoft Exchange Server Online. This functionality is not supported with Exchange Server 2019.
The WorkZone Meeting pane for a new meeting loads forever (macOS only)
On macOS machines, if the Outlook meeting does not contain any text in the email body, the WorkZone Meeting pane will be stuck on loading.
Workaround: When creating a new meeting event, add some text to the email body before opening the WorkZone Meeting pane.
WorkZone 365 add-in fails to load upon switching to a different user account
When you switch to a different user account, the WorkZone 365 add-in fails to load, showing the '404' error. This happens, because WorkZone 365 stores information to get the token for your user account in the local storage, but it is not invalidated when you switch to a different user.
Workaround: Clear the Office cache, as described in this Microsoft article.
Merge does not work for merge fields inside the page headers or shapes (Office 2019/ 2021 only)
When you try to merge WorkZone information into a Word template, no data is merged for the merge fields placed inside the page header or within shapes. This happens, because API is not supported for Office
Workaround: Upgrade your Word application to a later version, or use the Merge as copy option to merge the needed WorkZone information. See Merge as copy.
WorkZone Meeting agenda is the same for all meetings in the series
When you create an appointment series in your Outlook calendar and save any of these appointments to WorkZone, they all share the same agenda and represent the same WorkZone meeting.
WorkZone Process
SmartPost: Important if you upgrade from 2024.1 or earlier releases to 2026.0
If you upgrade from 2024.1 or earlier releases to 2026.0 and use SmartPost, you must cancel running SmartPost processes and restart them using the Send SmartPost dialog (not from the Processes Overview). This is to ensure that SmartPost uses the upgraded NgDP dispatcher.
The reason for restarting the SmartPost processes is that in 2024.1, an HTTP error 429 may occur when getting receipts due to changes of the Digital Post API from Digitaliseringsstyrelsen. The 429 error is shown in the history document. Upgrading to 2026.0 does not fix the issue for running SmartPostprocesses that were started in 2024.1, but new SmartPost processes that are started after the upgrade do not result in this error.
SmartPost: The PDF/UA validation of the merged documents does not always work if the attachments have different file formats
If the SmartPost message contains attachments with different file formats, for example Word and PDF documents, the first PDF/UA validation of the original documents is successful, but the second PDF/UA validation that validates the merged document sometimes fails due to an Aspose issue. The merged document is generated but it is not PDF/UA compliant. A correction is pending Aspose at the time of this release.
You can click Approve in the task/smartmail to send the message with a non-PDF/UA compliant document or cancel the process and disable PDF/UA before you start a SmartPost process with attachments of mixed file formats.
Searching for contacts fails in the Submission (Extended) process
When users try to forward a submission task by using the Forward button, the search for the contact to forward to fails when the there is a large number of contacts. The issue occurs when opening the Approve Submission task from Outlook when there is a large number of contacts on the list. The search works when opening the Approve Submission task from WorkZone Client.
The default deadline of the extended distribution process in Ministerial and Parliamentary Question processes is overwritten by the phase process settings
If you have specified a default deadline for the Extended distribution process, it will be ignored when the process is started automatically as part of the distribution phase of the Ministerial and Parliamentary Question phase processes. Only the default deadline of the phase process applies.
MunicipalityIdentifierFilter parameter is optional but should be mandatory
When you upgrade to WorkZone 2025.0 or later it is required that the MunicipalityIdentifierFilter parameter is filled in. The parameter cannot be empty despite the parameter listed as optional. The documentation has been revised accordingly. See Configure an Update municipality party service subprocess.
Case monitoring: A rule set that includes starting the Update Municipality Party service subprocess should not include other rules if the AllowCaseMonitorOnUpdatedCase parameter is turned on
If you have entered a date in the CasesCreatedFrom parameter in the Case monitoring process parameters and the selected rule set includes a rule that starts the Update Municipality Party service subprocess, and you have turned on the AllowCaseMonitorOnUpdatedCase parameter in the Update Municipality Party service subprocess, you should only have this rule turned on in the rule set. If there are additional rules, the rules can be activated on cases that are from before the date specified in the CasesCreatedFrom parameter.
Tasks are open in WorkZone for Office after takeover of the tasks
When a user takes over another user’s task or refreshes a task in WorkZone for Office while the task is locked by another user, the task is sometimes open for editing for both users.
SmartPost does not remerge recipient information when contacts are updated
When SmartPost is configured with the RemergePdfEnabled and AllowOfficeRemerge settings enabled in WorkZone Configurator, it is expected that SmartPost remerges recipient fields whenever contact information is changed, for example if a contact’s type or name is changed. However, SmartPost does not remerge the recipient merge fields and continues to send the message with the original recipient information in both the file name and merge fields.
WorkZone Mass Dispatch
Important if you upgrade from 2024.1 or earlier releases to 2026.0
If you upgrade from 2024.1 or earlier releases to 2026.0 and use WorkZone Mass Dispatch, you must complete all mass dispatch processes before you upgrade. Any active mass dispatch processes will not continue to run after the upgrade.
Messages are not sent if their recipient cases are deleted during an ongoing Mass dispatch process
If a user deletes the case template, the default case, or any of the recipient cases that are specified in the Cases sheet sheet, while the Mass dispatch process is running, the messages that had these cases as recipient cases will not be sent. The Mass dispatch process completes successfully but no error message is shown to the user or in the history document.
To avoid this issue, do not delete recipient cases that are mapped to contacts in the Case sheet, the case template, or the default recipient case.
Mass dispatch processes fail if a contact that exists in the recipient list is deleted
Mass dispatch processes fail if a contact that exists in the recipient list is deleted while the process is running.
Mass Dispatch fails to send messages to recipients when contacts are updated
Mass Dispatch does not send messages to recipients whose contact information is changed, for example if a contact’s type or name is changed. Messages are successfully sent to all other recipients.
WorkZone Mobile (New)
Cannot edit WorkZone documents in Microsoft 365 apps (On-premises only)
When you try to edit a WorkZone document in the relevant Microsoft 365 app, the white screen appears.
Microsoft is currently working on a solution to resolve this issue.
(
only): App crashes or shows the white screen after long idle time
Workaround: Try to avoid running the WorkZone Mobile (New) app idle (without doing anything in the app) for more than 3-4 days. If the issue still occurred, reinstall the WorkZone Mobile (New) app manually.
( only): Filter for a hearing task attachments and Browse icon do not work
Workaround: This will be fixed in the upcoming versions. You can perform the needed actions in WorkZone Client.
( only): Collapsed sections of Upcoming and Closed tasks expand when you pull to refresh
This will be fixed in the upcoming versions.
( only): Cannot update a parallel task forwarded to one of the approvers
If multiple approvers edit the parallel task (Advanced submission) at the same time, and one of them forwards the task to another, that user will receive a "Do you want to save your changes?" message with Cancel and Save buttons, but clicking on either button will do nothing.
Workaround: Switch to any other task, and then go back to the task in question to get its latest changes.
( , Intune only): Cannot load document edits made in Microsoft 365 Copilot app
When you edit a WorkZone document via relevant 365 Copilot app, and then open that document in WorkZone, your annotations are not displayed, and sometimes the white screen appears.
Microsoft is currently working on a solution to resolve this issue.
( only): Log-in fails, if you switch to another WorkZone server URL
If you try to switch to another WorkZone server URL (for example, if your organization uses more than one WorkZone servers) shortly after successfully logging in to a different WorkZone server URL, the log-in fails.
Workaround: Close and restart the WorkZone Mobile (New) app, and then enter the new URL.
( only): No confirmation dialog for canceling some PDF annotations
If you click Cancel for PDF annotations made via red pencil drawing, some marker drawing, or text insertions, there is no confirmation dialog asking if you are sure that you want to cancel these changes.
Workaround: As the last annotation, use one of the markers that do not cause this issue (for example, the yellow marker).
( only): Parliamentary Question tasks do not work
Tasks that have the Parliamentary Question process type are currently not supported in the WorkZone Mobile (New) app.
( only): Incorrect number of processing documents after adding a new document
If you add a new document to a task, then perform a non-final submission step, and then pull to refresh, the counter of processing document displays random number.
Workaround: Close and restart the WorkZone Mobile (New) app.
( only): Marker annotations are not saved in the Cancel > Save flow
If you make PDF annotations via marker drawing, then tap Cancel, and select Save, your changes are not saved.
Workaround: After making marker drawing annotations, switch to another annotation tool (for example, text highlight, or adding some text) before saving your changes.
( only): Cannot view SmartPost task documents with disabled PDF/UA validation
When you try to view a task document that has disabled PDF/UA validation, the document does not open.
Workaround: You can view such documents in WorkZone Client.
(, Intune only): Logout button sometimes does not work
Sometimes the Logout button does not work.
Workaround: Close and restart the WorkZone Mobile (New) app.
WorkZone Mobile (Legacy)
Documents cannot be opened from the SmartPost PDF/UA validation failed task
It is not possible view documents from a SmartPost PDF/UA validation failed task in WorkZone Mobile (Legacy).
To view documents and correct PDF/UA errors, you can open the original documents from the SmartPostPDF/UA validation failed task in WorkZone Client or Outlook. See Send PDF/UA compliant documents.
Cannot edit WorkZone documents in Microsoft 365 apps (On-premises only)
When you try to edit a WorkZone document in the relevant Microsoft 365 app, the white screen appears.
Microsoft is currently working on a solution to resolve this issue.
Citizen Access
Error when trying to access cases and documents - disabled feature
If you get the error message "404 Not Found" when trying to access cases and case documents through a client, portal, or form, it is because the WorkZone Citizen Access IDS enabled feature is not enabled in WorkZone Configurator. To enable it, go to Global > Feature settings > WorkZone Citizen Access.
Error when trying to access cases and documents - invalid credentials or unauthorized user
If you get the error message "405 Internal Server Error " when trying to access cases and case documents through a client, portal, or form, it means that the access is denied due to invalid credentials, or you may not be authorized to access WorkZone cases and documents. This error will occur when an invalid token is passed.
WorkZone PDF
PDF rendering fails with Japanese characters
The rendering of PDF documents fails if the WorkZone PDF Engine and WorkZone PDF Crawler configurations for header, footer, and watermark contain Japanese characters.
An incorrect error message is displayed: “The document may be password protected or corrupted. Check that the document is not corrupted and try again. You can view the errors in the preview pane”.
"504 Gateway timeout" error when generating large Classification Scheme reports
When generating a Classification Scheme report containing approximately 5000 entries or more, the report generation fails with a "504 Gateway timeout" error.
WorkZone Export/Import
Version command returns incorrect value
When you run the command "Kmd.WZIE.exe --version", WorkZone Export/Import will display "1.0.0" as the version number.
This number, though displayed, is incorrect.
Workaround: To see the correct version number, go to the Kmd.WZIE.exe your file explorer, right-click the file and go to Properties > Details, where you can se the correct version number in the File version field.
WorkZone Export/Import displays an inconvenient amount of warnings in the console
When running an export/import job, the WorkZone Export/Import.exe program displays warning messages both in the console and in the log file. Warnings should only be logged in the log file.
FK access
Very large FK Claims (having more than 100 http://sts.kombit.dk/constraints/orgenhed/1 entries) are not supported and can lead to errors during data restriction filtering.
This issue only affects municipality customers.