Click on any published known bug listed below to view a detailed description, including the issue's specifics, potential workarounds, and the planned version for its resolution.
Description:
On business modules that use Multiple Stage Models, creating an entity can fail if one of the stage models has no value in the stage model mapping field. A typical example is an existing Default model. This happens even when the stage model and start stage you selected are correctly mapped. The user sees a generic error ("Processen mislykkedes"), and the details show "Nullable object must have a value."
Cause:
When entity creation looks up the selected stage model, it fails if it encounters a stage model without a mapping value. An unmapped Default model is a supported configuration, so this has been confirmed as a bug.
Workaround:
Give every stage model on the business module a value in the mapping field, including the Default model. Entity creation then works as expected.
Status:
We are aware of this issue, and a fix is planned. Until the fix is available, use the workaround above.
Description:
When the WorkPoint Administration dashboard is opened from the Admin Portal, selecting "Go to [module] list" in a business module's menu does not open the SharePoint list. Instead, the page shows a broken-page icon and a "refused to connect" error. This affects all business modules.
Cause:
"Go to list" tries to open the SharePoint list inside the embedded Admin Portal view. SharePoint and the Microsoft sign-in page do not allow themselves to be shown in an embedded view, so the browser blocks the page.
Workaround:
In the same module menu, select "List Settings", then click the module name in the page heading to open the list.
Status:
We are aware of this issue, and a fix is planned. Until the fix is available, use the workaround above.
Description:
When you configure a Create Entity step under the "Entity not found" branch of a Mail Assistant process in the Process Builder, the Context browser doesn't show the email properties from the Mail Assistant output, such as subject and sender domain. This happens even when Step Input is set to "Output from Mail Assistant". The same properties are shown as expected on the Upload email step in the same process. As a result, Create Entity fields such as Title, lookup values and metadata can't be bound to email properties through the Context browser.
Cause:
The email properties are not loaded into the Context browser for the Create Entity step in this branch. This has been confirmed as a bug.
Workaround:
Enter the email tokens manually in the Create Entity step's fields, for example {Element.subject}. Note that manually entered tokens are not validated and have no IntelliSense, so check that they are spelled correctly.
Status:
We are aware of this issue, and a fix is planned. Until the fix is available, use the workaround above.
Description:
In some solutions, the Site Collection Synchronization job may time out or remain running without completing. The job can stall while attempting to activate the deprecated SharePoint feature VivaTopicsConfigData.
Cause:
The Site Collection Synchronization attempts to activate the deprecated VivaTopicsConfigData feature. This prevents the synchronization job from completing successfully.
Workaround:
Disable Viva Topics on the root site for the affected solution and run the Site Collection Synchronization again.
Status:
We are aware of this issue. A product fix is planned to ensure that deprecated Microsoft features are handled correctly. Until the fix is available, use the workaround above.
Description:
We have identified an issue where a Document ID assigned by the Numerator Service may disappear after a Word document is uploaded or created and the user continues editing it with AutoSave enabled.
Cause:
The Numerator Service updates the Document ID column in SharePoint after the document is added. If the document remains open, a later AutoSave can trigger synchronization of document properties between Word and SharePoint. If the value stored inside the Word document is empty or outdated, SharePoint can promote that value back to the corresponding column and overwrite the Document ID assigned by the Numerator Service.
Workaround:
Disable SharePoint document property promotion for the affected libraries under Master Site Settings.
After updating the configuration, perform a Master Site Sync of the List Settings to apply the change to the relevant libraries.
Status
WorkPoint is aware of the issue and is evaluating a permanent solution. Disabling document property promotion is the recommended workaround until a fix is available.
Overview
It has been identified that certain Microsoft 365 tenants have activated Baseline Security Mode. While this feature enhances the security posture of a tenant, it currently introduces a limitation regarding Custom Scripts across all sites.
When this mode is active, Microsoft 365 enforces a restriction that prevents the temporary enablement of custom scripts, which is currently required for specific WorkPoint 365 operations.
Impact on WorkPoint 365
WorkPoint 365 utilizes custom script capabilities to perform essential configuration tasks. If Baseline Security Mode is enabled, the following processes are currently affected:
- Entity Management: Setting the NoCrawl property on a Web when an entity is deleted or restored.
-
Provisioning & Sync: * Connecting entities and sites through the Web Property Bag during site creation or Master Site sync.
- Setting Site Collection properties during initial creation.
- Syncing property bag entries at the Site Collection level.
- App Lifecycle: Installing or updating the Modern UI app within the Tenant App Catalog.
- Buffer Site Management: Updating the ServerRelativeUrl when buffer sites are taken into use.
Future Support & Roadmap
WorkPoint is committed to supporting Microsoft's security standards. We are currently developing updates to our core engine to ensure full compatibility with Baseline Security Mode.
Future releases will transition these processes to methods that do not rely on custom scripts, allowing you to maintain a high-security baseline without impacting WorkPoint functionality.
Recommendation
If you experience issues with site provisioning or property syncing, please verify if Baseline Security Mode is active in your tenant:
- Navigate to Settings > Org Settings in the Microsoft 365 Admin Center.
- Go to the Security & Privacy tab.
- Check the status of Baseline Security Mode.
- If enabled, we recommend making adjustments, to ensure custom script capabilities aren't blocked.
Description:
When creating a buffer site or a new site collection, the operation fails with an exception stating that activation of the SharePoint Server Publishing Infrastructure feature is not allowed.
The complete message:
“Error when activating Site Collection feature SharePoint Server Publishing Infrastructure Activation of classic publishing feature is not allowed.”
This behavior occurs if the feature is active on the master site collection.
Cause:
Starting September 15, 2025, Microsoft has disabled creation of new classic publishing sites and blocked activation of publishing features in SharePoint Online. This change is part of Microsoft’s modernization strategy and applies to both user interface and API-based site creation.
Existing classic publishing sites continue to work as usual, but new classic publishing sites cannot be created, and publishing features can no longer be activated on new site collections.
Workaround:
If classic publishing features are not in use, disable them on the master site collection. After disabling the feature you also need to ensure that the list ReusableContent is hidden on the master site.
If publishing features are required temporarily, tenant administrators can enable the following setting via PowerShell until March 15, 2026:Set-SPOTenant -AllowClassicPublishingSiteCreation $true
Status:
This is expected behavior due to Microsoft’s enforcement of modern SharePoint site standards. WorkPoint recommends disabling the Classic Publishing Feature on the Master Site Collection if not in use.
Description
When configuring a process in WorkPoint Automate with the "Copy or move documents" step configured to run in "Move Mode" the modified date of the moved document is not preserved.
Workaround
Currently there is no workaround.
Status
Known limitation.
Description
When running a WorkPoint Automate process that includes document conversion to PDF, an error may occur when processing a large number of documents or handling large file sizes.
The following error message will be displayed:
Workaround
The "Converts selected documents to PDFs" should be set to run async:
Status
Known bug. Better error message if there is time out on the API due to the file size. User should be informed that they must run the process async.
Comments
44 comments
Known bugs and limitations updated.
Known bugs and limitations updated.
Known bugs and limitations updated.
Added: Web Parts Not Working on Modules After Import to a New Tenant (ID46661) and Copy or move documents Step in Move Mode does not preserve Modified date (ID46725)
Known bugs and limitations updated.
Added: SharePoint Group Sync Fails on Bucket Site Collection if Root Site Title is in Group Name (ID46775)
Known bugs and limitations updated.
Added: UnauthorizedAccessException when generating PDF without Default PDF Format saved (ID46858)
Known bugs and limitations updated.
Added: WorkPoint Express does not load in the right task pane in Microsoft Word version 2502 (Current Channel) (ID45193)
Known bugs and limitations updated.
Updated: WorkPoint Automate Process not triggering on 'When an Item is Published' (ID43574)
Known bugs and limitations updated.
Resolved in version 4.23
Known bugs and limitations updated.
Changes to Search Settings on a Master Site are not synchronized during site creation (ID44879) moved to 4.25
Hi, question on ID45193.
When is WPE 6.11.1 planned for release?
Hi Bjørn
Testing have just been completed, so in the near future the release will be ready.
Hi Per.
Do you have any ETA on WPE 6.11.1?
Hi Jakob
After Easter.
Known bugs and limitations updated.
WorkPoint Express does not load in the right task pane in Microsoft Word version 2502 (Current Channel) (ID45193)
Hi Per, ID45193?
Will you release a WorkPoint Express Hotfix 6.11.1 for 32 bit Office edition?
Known bugs and limitations updated.
WorkPoint Express does not load in the right task pane in Microsoft Word version 2502 (Current Channel) (ID45193) (added 32bit Office download option)
Known bugs and limitations updated.
Incorrect Logging Start and End Time in WorkPoint 365 Admin Logs (ID46284) - Planned release date added.
Known bugs and limitations updated.
Added:
Teaching bubble and navigation doesn't work on sub process (ID47317)
Access denied when removing deletion mark from site in Entity Site Recycle bin on NoScript sites (ID47292)
Moved to resolved in version 4.24 (being released tonight):
Adding a Period (".") in Document Title Changes File Extension in UI (ID45707)
Importing a Solution Fails with NullReferenceException (ID45885)
Moved to archive:
WorkPoint Express does not load in the right task pane in Microsoft Word version 2502 and later (Current Channel) (ID45193)
Hi Per
Will the WPE download page be updated with version 6.11.1? :-)
Hi Jakob
Download links are provided in:
https://support.workpoint.dk/hc/en-us/articles/360020935093-Known-bugs-and-limitations#workpoint-express-does-not-load-in-right-task-pane-microsoft-word-version-2502-later-id45193
They are not planned to be included on the main download site, since it only affects a subset of Word editions.
Known bugs and limitations updated.
Updated:
Process Fails to Load When Run from Business Module List through Microsoft Lists Web View" (ID46095)
Known bugs and limitations updated.
Added:
Parent Entity Title Not Displayed in Lookup Field During Process Execution (ID47709)
Known bugs and limitations updated.
Added:
Misleading Timeout Exception for Completed Web Jobs (ID47697)
Known bugs and limitations updated.
Moved to resolved in version 4.25 (being released tonight):
SharePoint Group Sync Fails on Bucket Site Collection if Root Site Title is in Group Name (ID46775)
Clarify Connection Requirement in WorkPoint Automate (ID46347)
Incorrect Logging Start and End Time in WorkPoint 365 Admin Logs (ID46284)
Content Column Disappears When Lock is Hidden in Copy Entity Form (ID46094)
Tenant-Wide Search Not Properly Managed by the Search Form Step (ID46082)
Deleting failed jobs from the WorkPoint Job Queue fails (ID45886)
WorkPoint Automate: Incorrect Date Format in Search Form Process Step (ID46132)
Changes to Search Settings on a Master Site are not synchronized during site creation (ID44879)
Known bugs and limitations updated after 4.26 release.
Known bugs and limitations updated.
Added:
Copy entity removes Quick Navigation elements linking to site pages (ID48374)
Known bugs and limitations updated.
Added:
PDF Combine Fails When Page Sizes Differ (ID48472)
Known bugs and limitations updated.
Added:
Teams Tab Links on Master Site Point to Master Resources Instead of Entity-Specific Ones (ID48504)
Known bugs and limitations updated.
Added:
WorkPoint Process Step Loses Configuration When Switching Between Two 'Send HTTP Request' Steps (ID48523)
Known bugs and limitations updated.
Added:
Outlook Actionable Adaptive Card Emails Render Blank in Specific Mail Flow Configurations (ID48555)
Please sign in to leave a comment.