---
title: "BizTalk360 - Known Issues"
slug: "known-issues"
updated: 2026-07-10T09:19:37Z
published: 2026-07-10T09:19:37Z
canonical: "docs.biztalk360.com/known-issues"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.biztalk360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# BizTalk360 - Known Issues

### Version 11.8

- Monitoring Service auto-restart tasks take more time compared to the configured time when the BizTalk360 IIS application pool becomes idle due to prolonged UI inactivity - Fixed in 11.9
- An "Exception occurred when fetching the service status" of Analytics and Monitoring Services was intermittently logged in BizTalk360 - Fixed in 11.9

### Version 11.7

- Automated Tasks failed for gMSA accounts with the error: "Authentication Failed for User." Automated Task execution was updated to remove dependency on the service account being added to Team Management. - Fixed in 11.9
- Server permissions in Manage Infrastructure (BizTalk/SQL Servers) were not recognized when the BizTalk360 service account was added through a nested Local Administrators group. Nested group membership support was added. - Fixed in 11.9
- BHM Profile and IIS Server Configuration: “Object reference“ exception occurred in Environment Settings when saving the BHM profile and IIS server configuration. - Fixed in 11.8
- Exceptions in Monitoring Service subservices were not reflected on the Manage Services page, causing the Monitoring Service status to appear unhealthy despite underlying services being healthy. - Fixed in 11.8
- Issue where alarm statistics, including alarm count and status, were not displayed correctly in the Environment Details card on the landing page. - Fixed in 11.8

### Version 11.6

- Authentication exceptions occurred while repairing orphaned DTA service instances through Automated Tasks. Enhanced authentication handling across multiple servers for the BHM Maintenance Automated Task - Fixed in 11.9
- Message Box content viewing support in high-availability environments where BizTalk Server instances are distributed across multiple locations. - Fixed in 11.8
- An issue where alert notifications failed to trigger after migration from older versions due to a newly introduced property in the email template. - Fixed in 11.8
- Tracking queries throw an access-related exception for non-super users. - Fixed in 11.7
- BizTalk360 Home page load time is due to a large set of Host Instances. - Fixed in 11.7
- Tracked Message Events to display promoted properties correctly. - Fixed in 11.7

### Version 11.5

- An Import/Export issue where dashboards sharing the same name across Analytics, EDI, and BAM categories were overwriting dashboards in other categories. - Fixed in 11.7
- Inconsistent Administration dashboard layout and its widgets while editing. - Fixed in 11.7
- Server marked as not reachable when a standalone single server is configured as a cluster in the SQL Server configuration. - Improved in 11.7
- An issue where an empty environment entry appeared when the SQL Instance name was not specified. - Fixed in 11.6

### Version 11.4

- UI issue where the Monitoring Service status was incorrectly displayed as "Server Down" even when the service was running normally. - Fixed in 11.7
- An issue where automated task auditing failed due to character length restrictions in the Username column. - Fixed in 11.6

## Related

- [v11.6](/v116.md)
- [v11.5](/v115.md)
- [v11.7](/v117.md)
- [v11.8](/v118.md)
- [v11.4](/v114.md)