Skip to content

Commit a7b39cd

Browse files
Merge pull request #303992 from PatAltimore/patricka-event-grid-websocket
Remove IoT Operations known issue 8891
2 parents 477d2fe + f2f11bc commit a7b39cd

File tree

1 file changed

+1
-17
lines changed

1 file changed

+1
-17
lines changed

articles/iot-operations/troubleshoot/known-issues.md

Lines changed: 1 addition & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Known issues for the MQTT broker, Layered Network Management (previ
44
author: dominicbetts
55
ms.author: dobett
66
ms.topic: troubleshooting-known-issue
7-
ms.date: 07/30/2025
7+
ms.date: 08/07/2025
88
---
99

1010
# Known issues: Azure IoT Operations
@@ -287,22 +287,6 @@ Data flow custom resources created in your cluster using Kubernetes aren't visib
287287

288288
There's currently no workaround for this issue.
289289

290-
### Connection failures with Azure Event Grid
291-
292-
---
293-
294-
Issue ID: 8891
295-
296-
---
297-
298-
Log signature: N/A
299-
300-
---
301-
302-
When you connect multiple IoT Operations instances to the same Event Grid MQTT namespace, connection failures might occur due to client ID conflicts. Client IDs are currently derived from data flow resource names, and when using infrastructure as code patterns for deployment, the generated client IDs might be identical.
303-
304-
To work around this issue, add randomness to the data flow names in your deployment templates.
305-
306290
### A data flow profile can't exceed 70 data flows
307291

308292
---

0 commit comments

Comments
 (0)