Product status
Known issues and limits
Check whether a problem is a confirmed bug, a documented data limit, or a Power BI environment restriction.
Version scope: Threadseer 1.1.0.8 · Last reviewed: October 7, 2026
Known issues
The public GitHub tracker lists confirmed current bugs with the known issue label. If the filtered list is empty, there are no confirmed open issues with that label.
Report filtering
Case-cohort report filters support up to 25,000 distinct Case ID values and a 1 MB payload. Larger selections stay internal or use an available exact-event selection, with the active behavior stated in the visual. Date-valued Case IDs or an unresolved source column can require that fallback. Threadseer never sends a truncated case cohort. Reanalyze a stale snapshot before filtering the report from it. Report totals can include source records excluded from the mined snapshot by data-quality rules.
If Power BI does not confirm a report-filter update, Threadseer explains that the exploration was not saved. Clear the selection and retry. Genuine changes from report or page filters still require explicit reanalysis.
Product limits
Appearance settings accept color values, not image or paint references. Invalid color values use default colors. If imported formatting looks different, choose a valid color again in the Format pane.
The saved analysis tab can restore with matching input. Changed input still requires explicit analysis, and bookmarks with Data disabled do not change the current tab. Update older bookmarks after arranging the desired exploration.
Bookmarks require Data enabled and Threadseer included in the bookmark. Data-dependent selections, expanded groups and zoom restore only against matching analyzed input. Explicit bookmark cohorts are limited to 4,096 case indexes and map search text to 2,048 characters; a visible notice explains when a selection is too large to save. Other tabs' searches, sorting and scroll position are not saved.
Data size
- Community supports up to 25,000 event rows in each analysis.
- Professional has a supported baseline of 100,000 event rows.
- Professional may attempt complete datasets above 100,000 rows, up to 1,000,000, when Power BI and device resources permit. Larger analyses are not guaranteed.
- If Power BI cannot load the full filtered dataset, Threadseer stops instead of analyzing partial data.
- A read-only dashboard tile may receive only the first 10,000 events from a larger selection. Threadseer keeps Analyze disabled and directs you to the source report instead of loading indefinitely or analyzing incomplete tile data.
Process map
Very large numbers of activities or connections can make a process map difficult to read. Threadseer applies display limits to keep the workspace usable. Narrow the Power BI filters when the map is too dense.
Case details
The Cases view displays up to 200 matching cases at a time. A selected case timeline displays up to 500 events. Use search or another view to narrow a large group.
Filters and refreshed results
Selection changed means the displayed results still represent the previous selection, even if both row counts are equal. Compare the displayed and new row counts, then deliberately choose Analyze new selection to replace the results. Hover over or focus Snapshot details beside Process Explorer to check the analysis time.
Supported Power BI environments
Use Threadseer in Power BI Desktop or interactive Power BI Service reports. Report behavior also depends on the Power BI version, browser, visual size, and organization settings. Power BI Mobile apps are outside the supported environment scope.
Power BI does not offer individual dashboard pinning for slicer-style custom visuals such as Threadseer, which uses case filters to update other report visuals. To include Threadseer on a dashboard, pin the live report page. Open the source report for full analysis and filtering.
Threadseer needs event-row Case ID, Activity and Timestamp fields. A converted Gauge can keep its measures in setup, but those measures cannot be analyzed as events. Reassign or remove incompatible fields and choose Don't summarize for numeric event columns. If Power BI omits an assigned field from event rows, reassign it or add a fresh Threadseer and map the fields again.
Embedded reports, national or regional clouds, Power BI Report Server, and export features have additional Power BI or licensing limits. Do not assume they behave the same as Power BI Desktop or Service.
Licensing limits
Microsoft does not support licensed custom-visual plans in every Power BI environment. See Plans & Pricing for the current list.
Before reporting a problem
Try the quick troubleshooting steps and reproduce the behavior with synthetic data. GitHub issues are public, so do not attach operational, customer, confidential, account, or personal information.