01-02 February 2026: A license error occurred on Tuesday afternoon (02/02/2026) as well as on Monday morning. The error was caused by a brief connection glitch between AppSource and our license API. The issue lasted only a very short time and resolved itself without any action required.
Based on this, we will be monitoring the situation more closely going forward. A recent change to the API is currently being rolled back, which we expect will resolve the issue permanently.
Please feel free to reach out if you have any further questions.
For urgent matters, you can also contact us at support@accobat.com, which is monitored continuously.
11 January 2026: The accoPLANNING Professional version (Version: 1.0.83.5) was deployed to AppSource. When using cell comments, the existing comment history is applied to the transaction together with the new comment. Please refer to the release log for available workarounds. (https://kb.accobat.com/kb/guide/en/1-0-83-5-accoplanning-wwDQFfVypG/Steps/4851995)
Self-hosted API and Chrome/Edge Compatibility – November 25, 2025
Following the latest Chrome/Edge update, compatibility issues have been identified affecting both Chrome and the self-hosted API. The root cause is Chrome’s implementation of stricter network security policies, which prevent the API from functioning correctly when visuals are rendered inside an IFrame.
Impact
The accoPlanning visual embedded in Power BI Service fails to communicate with the self-hosted API when accessed via Chrome/Edge.
Root Cause
Chrome's (Edge) new policy enforces enhanced restrictions on requests to private ip addresses, requireing explicit permission, which Powerbi does not pass down to their IFrames for visuals. Resulting in blocked API calls
Recommended Solution
For customers using the self-hosted API: Host the API on a public IP address or domain.
This is necessary because Chrome’s new network security policy blocks traffic to private IP addresses. By hosting the API on a public endpoint, you ensure compatibility and avoid disruptions caused by these restrictions.Disable Chrome’s Local Network Access policy:
This can be done by navigating to:chrome://flags/#local-network-access-checkand disabling “Local Network Access”.
Important: Looking ahead, the best long-term solution will be to add a dedicated public IP address or domain for the self-hosted API. We will update the documentation to reflect this.In the meantime, it should be acceptable to disable this policy for a short period. While it can theoretically reduce browser security, it has not been enabled by default by Google or Microsoft before now and has therefore not posed an issue in previous setups. This makes it reasonable to use this temporary workaround until the long-term solution is in place.
We always recommend that all customers verify this approach with their internal security responsibility instance, as IT security should be taken seriously in all environments.
EDGE Update December10, 2025
As of today, we can confirm that Edge has also been updated. This means that if you experience errors related to the API, you can do the following.
Steps to Disable Local Network Access Checks in Microsoft Edge
Open Microsoft Edge
Launch your Edge browser.Navigate to the Flags Settings
In the address bar, enter:edge://flags/
and press Enter.Locate “Local Network Access Checks”
Scroll down the list until you find the option Local Network Access Checks.Change the Setting
On the right-hand side, open the drop-down menu and select Disable.Restart Edge
After making this change, restart your browser to apply the new setting.
Prior issues:
11-12 January 2026:
A License API issue was identified that may have affected the solution on 11/01/2026. The issue was resolved shortly after it was reported.