Connections Troubleshooting
Data connections are the foundation. If data isn't flowing, start here.
Connections bring your data into OpenIndustrial. When they have issues, everything downstream stops. This guide covers common connection problems and their solutions.
Connection Health Check
Quick checks in order:
- Status indicator - Is the connection showing "Connected"?
- Data flow - Are you seeing incoming data?
- Timestamps - Is data recent (not stale)?
Common Issues
Connection Shows "Error"
Symptoms:
- Red status indicator
- No data flowing
- Error message in connection details
Diagnosis:
- Open the connection to see the error details
- Check the error message (see error reference below)
- Verify credentials are correct
Common causes:
- Credentials expired or rotated
- Network configuration changed
- Source resource deleted or modified
Connection Shows "Connected" But No Data
Symptoms:
- Green status indicator
- Surface shows no data
- Queries return empty
Diagnosis:
- Is the source actually sending data?
- Is the connection linked to the right surface?
- Check for data filtering issues
A "Connected" status means we can reach the source. It doesn't guarantee data is being sent by your devices or applications.
Data Is Delayed
Symptoms:
- Timestamps are old
- Data arrives in batches
- Real-time queries show stale data
Possible causes:
- Network latency
- Source batching behavior
- Time zone configuration
- Consumer group contention
Connection Types
IoT Hub Connections
Specific requirements:
- Connection string must be Hub-level (not device-level)
- Policy needs ServiceConnect permission
- Consumer group must be dedicated
Common mistakes:
| Mistake | Symptom | Fix |
|---|---|---|
| Device connection string | Auth fails | Use Hub connection string |
| Wrong policy | Permission denied | Use iothubowner or custom with ServiceConnect |
| Shared consumer group | Intermittent data | Create dedicated consumer group |
Event Hub Connections
Specific requirements:
- Connection string must include EntityPath
- Consumer group must exist
- Partition count matters for parallel reading
Common mistakes:
| Mistake | Symptom | Fix |
|---|---|---|
| Missing EntityPath | Resource not found | Add EntityPath to connection string |
| Consumer group missing | Connection fails | Create consumer group in Azure |
| Wrong namespace | Not found | Check namespace spelling |
Error Reference
"Invalid connection string"
Cause: Malformed connection string format
Fix:
- Copy fresh from Azure Portal
- Don't modify the string
- Check for truncation
"Authentication failed"
Cause: Invalid or expired credentials
Fix:
- Verify key in Azure Portal
- Update connection with new key
- Check policy permissions
"Consumer group not found"
Cause: Specified consumer group doesn't exist
Fix:
- Create consumer group in Azure
- Use existing consumer group name
- Default is "$Default"
"Connection timeout"
Cause: Network or firewall issue
Fix:
- Check network connectivity
- Verify firewall allows OI IPs
- Check proxy settings if applicable
Creating New Connections
Two ways to create:
- Drag-and-drop - Create connection widget, configure manually
- Ask Azi - "Create a connection for my IoT Hub"
Either way, Azi validates your configuration before applying changes.
Testing Connections
Before relying on a connection:
- Verify data source is sending data (check in Azure Portal)
- Create connection in OpenIndustrial
- Link to a test surface
- Build a simple query:
YourTable | take 10 - Verify data appears
Start with the simulator for testing your setup. Switch to real connections once you're confident in the flow.
Ask Azi
In chat, try:
- "Why is my IoT Hub connection failing?"
- "Help me configure an Event Hub connection"
- "Diagnose this connection error: [paste error]"
Related
- Can't Connect - Authentication and connectivity issues
- No Data Showing - When connection works but no data appears
- Surfaces Troubleshooting - Issues with surfaces linked to connections
On this page
- FrontmatterVersion: 1 DocumentType: Guide Title: "Connections" Summary: "When data stops flowing, check the status indicator, the freshness of your timestamps, and the error reference for connection failures." Created: 2026-01-19
- Connections Troubleshooting