Help center
Get help with Threadseer
Try a few quick checks, review known issues, or tell us what happened using a safe synthetic example.
Troubleshoot a problem
Start with the quick checks below and the Getting Started guide.
Report a bug
Use the public bug form for behavior you can reproduce without sharing real operational data.
Open the bug form →
Suggest an improvement
Describe what you are trying to accomplish and what a better outcome would look like.
Request a feature →
Before you share anything: GitHub issues are public. Do not upload real event logs, Power BI report files, screenshots with case identifiers, tenant details, personal information, credentials, or proprietary field names. Use a blank report and synthetic data.
Quick troubleshooting
- Confirm that Case ID, Activity, and Timestamp point to the intended columns.
- Check that timestamps use a consistent data type and contain valid values.
- Choose Analyze or Reanalyze after changing fields or Power BI filters.
- If a dashboard tile directs you to the source report, open or refresh that report before retrying; the tile may not contain the complete filtered selection.
- Try the same steps in a blank report with a small synthetic dataset.
- Review the known issues and limits.
What to include in a bug report
- Your Threadseer version. Find it in the PBIVIZ filename or, after public release, in the Marketplace/version information supplied with the visual. Threadseer does not currently include an in-visual About page.
- Your Power BI environment—Desktop, Service, or embedded—and its version.
- The exact steps that reproduce the problem using synthetic field names and data.
- What you expected and what actually happened.
- Whether the problem also occurs in a blank report.
A GitHub account is required, and you must sign in before opening an issue. Anyone can browse existing issues. If you received a private Professional Preview and cannot use GitHub, reply to the pilot invitation instead.
Report a security concern privately
Use private vulnerability reporting for suspected security vulnerabilities. Do not post security details in a public issue, and do not use this channel for ordinary support.
Account, purchase, legal, or privacy questions
Do not put personal, account, purchase, licensing, legal, or privacy-rights information in a public issue. A verified private support and privacy contact, along with the Marketplace contact path, will be published before public sale. If you receive Threadseer through Microsoft before then, use the private publisher contact supplied with that distribution.
Support is provided on a reasonable-efforts basis. No response or resolution time is guaranteed unless a separate written agreement says otherwise.