Troubleshooting

Agent starts but doesn't appear in the dashboard

• Check your firewall: Ensure outbound HTTPS (port 443) is allowed to summitview.app
• Check the console output: Look for error messages in the agent console window
• Verify authentication: If you see "Authentication failed", try running with --reauthenticate
• Check proxy settings: If your network uses a proxy, the agent will use the system proxy settings automatically

Agent shows "Offline" in the dashboard

• The agent sends a heartbeat every 30 seconds. If no heartbeat is received for 5 minutes, it shows as offline.
• Verify the agent process is still running (check Task Manager)
• If running as a Windows Service, check the service status: sc query SummitViewAgent

"AADSTS700016: Application not found"

This means the SummitView Agent app registration isn't available in your tenant.

• Ensure you're signing in with a work or school account (not a personal Microsoft account)
• Contact your Azure AD administrator to allow the SummitView Agent application

Sign-in succeeds but no data appears

• Check workspace access: The signed-in user needs at least Contributor access to the workspaces
• Wait a few minutes: Inventory sync runs every 15 minutes. Refresh data appears when new refreshes complete.
• Check the Permissions page: Go to Agents and check the permissions status for your agent

Need to switch to a different user account

Run the agent with the --reauthenticate flag to clear the cached token and sign in again:

SummitView.Agent.exe --reauthenticate

Usage analytics or capacity metrics not appearing

These features require admin consent:

• Usage Analytics requires Tenant.Read.All permission with admin consent
• Capacity Metrics requires Capacity.Read.All permission with admin consent
• The signed-in user must have the Power BI Admin role in Microsoft 365

Per-table timing not showing for some workspaces

• Per-table timing requires PPU, Premium, or Fabric workspaces
• Pro workspaces only get basic refresh status (no per-table detail)
• Verify the XMLA read/write endpoint is enabled in your capacity settings (Power BI Admin Portal → Capacity settings)
• The user needs at least Contributor access to the workspace

"XMLA endpoint not available"

• Verify the workspace is on Premium Per User, Premium, or Fabric capacity
• Check that the XMLA read/write endpoint is enabled:
  Power BI Admin Portal → Capacity settings → XMLA Endpoint → set to Read Write or Read Only
• Ensure your firewall allows outbound HTTPS to *.analysis.windows.net

XMLA falls back to REST polling

This is normal for Pro workspaces. The agent will automatically use REST API polling when XMLA is not available, providing basic refresh monitoring without per-table detail. This is not an error.