Application not connected to the IAPM backend, or no instrumented services sending data
Verify your connection to otlp.iapm.app on port 443. Confirm your instrumented applications are configured to send OpenTelemetry data to the correct endpoint. See Network Requirements below.
"Connection failed" error
Firewall or proxy blocking outbound HTTPS traffic
Ensure ports 443/TCP are open for all endpoints listed in Network Requirements. If behind a corporate proxy, configure the proxy settings in your system environment variables.
Data stops updating after a while
Network interruption or session timeout
Check your network connection. The application will automatically reconnect when connectivity is restored. If the issue persists, restart the application.
Demo telemetry not loading
Demo mode not enabled or backend unreachable
Open Settings > Data Source and confirm Demo Telemetry is selected. Verify you have an active internet connection to api-azure.iapm.app.
Reduce the data density by narrowing the time range filter. If you have very high-throughput services, consider filtering to specific service namespaces.
No active internet connection or backend service temporarily unavailable
Verify connectivity to api-azure.iapm.app on port 443. Check the connection status indicator in the Tessa chat panel.
Voice commands not recognized
Microphone not configured or browser permissions not granted
Ensure your microphone is set as the default input device in your OS audio settings. Grant microphone access when prompted by the application. Check Settings > Audio > Input Device.
Energy depleted message
AI usage quota has been consumed for the current period
Energy replenishes automatically over time. You can continue using IAPM 3D without AI features while energy recharges. Check your current energy level in the Tessa panel.
Chat history lost
Session ended or application was closed without saving
Chat history is tied to the active session. Starting a new session begins a fresh conversation. This is expected behavior - Tessa maintains context only within a single session.
SteamVR not installed or headset not properly connected
Install SteamVR and verify your headset appears in the SteamVR dashboard before launching IAPM 3D. Check USB and DisplayPort/HDMI connections.
Motion sickness / discomfort
Sensitivity to smooth locomotion or low framerate in VR
Enable Comfort Mode in Settings > VR to use teleportation-only movement. Ensure your system maintains 90 FPS in VR - lower the graphics quality if needed. Take regular breaks.
Controllers not mapping correctly
Non-default controller bindings or unsupported controller model
Reset controller bindings to defaults in SteamVR > Settings > Controllers > Manage Controller Bindings. IAPM 3D currently supports Meta Quest (via Quest Link) and HTC Vive controllers.
Blurry or distorted display in VR
Headset IPD not adjusted or render resolution too low
Adjust the IPD (inter-pupillary distance) on your headset. Increase the render resolution in SteamVR > Settings > Video > Render Resolution.
Browser cookie or cache issue preventing OAuth completion
Clear your browser cache and cookies for portal.iapm.app. Try using a different default browser. Ensure pop-ups are not blocked for the authentication domain.
Session expired frequently
System clock out of sync or unstable network connection
Verify your system clock is accurate and set to auto-sync. Check that your network connection is stable - frequent disconnects will invalidate sessions.
Browser-based auth not opening
Default browser not configured or blocked by security policy
Set a default browser in your OS settings. If in a corporate environment, confirm that portal.iapm.app is not blocked by your organization's web filter. Try launching the auth URL manually from the login screen.
If your organization uses an HTTPS inspection proxy, ensure the above domains are added to the inspection bypass list. TLS inspection can interfere with real-time telemetry streaming.