Unknown ResourceLimitsPackageCountExceeded error

Hi gotters​,

When .pbix files are imported or cloned via Power BI Desktop or REST APIs, Power BI creates an Import entity alongside the Report and Semantic Model. Over time, publishing updates, overwriting reports, or deleting report visuals without deleting their underlying underlying import histories accumulates hidden "orphaned" import objects. Even though you only see ~500 visible reports in the UI, the total count of reports + hidden import packages has breached the 1,000 workspace threshold.

but while creating reports directly in the Power BI Service works: service-created reports only generate a thin report definition without creating a heavy .pbix upload package/import record.

To verify you should check the no. of items in your Group(Workspace) like Reports, datasets  and imports , chech details on these microsoft links.

Refer this thread on community if it helps you. 

🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUserand Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!

AI-assisted draft | Human-verified technical content

Thanks for the reply.
We checked all the above already via API.... 
Reports were the same as the UI, Datasets were 0 as expected. 
There were a good few hundred imports and if combind with the reports they were over 1000 however it didnt seem to be that the imports were simply counted as they appeared.
We suspected the imports might be contributing to the count but we dont know how and cant find any information how.
Also there is no way for us to clear out the imports. Many of them are orphaned, ie the associated report has been deleted.
So its not adding up and we cant find any info on this.
Please advise.
Thanks

Yes but we're facing what could be an ongoing issue so neither of those are good solutions.
We need a way to be able to track and monitor the REAL usage count so that we can tell when we're nearing limits.
How would we do that?
Does a tenant admin have access to see the real count (that the 1000 max works off). Ideally some kind of API access for a non-tenant admin would be what we need

Unresolved. Trying to raise a support ticket through our 3rd party support providers.

Hi gotters​,

On your follow-up about monitoring the real count: I don't know the exact internal formula the service uses for that limit, but since your symptoms line up with import records, the practical approach is to track reports + models + imports per workspace yourself and alert well before 1,000. The imports API is the part the UI never shows you. A scheduled PowerShell job can do it:

# Requires: Install-Module MicrosoftPowerBIMgmt
Connect-PowerBIServiceAccount
$threshold = 900
$ws = Get-PowerBIWorkspace -All

$report = foreach ($w in $ws) {
    $base    = "groups/$($w.Id)"
    $reports = (Invoke-PowerBIRestMethod -Url "$base/reports"  -Method Get | ConvertFrom-Json).value
    $models  = (Invoke-PowerBIRestMethod -Url "$base/datasets" -Method Get | ConvertFrom-Json).value
    $imports = (Invoke-PowerBIRestMethod -Url "$base/imports"  -Method Get | ConvertFrom-Json).value
    [pscustomobject]@{
        Workspace = $w.Name
        Reports   = $reports.Count
        Models    = $models.Count
        Imports   = $imports.Count
        Total     = $reports.Count + $models.Count + $imports.Count
    }
}
$report | Sort-Object Total -Descending | Format-Table
$report | Where-Object Total -ge $threshold   # alert on these

Run it with an account that is a member of the workspaces (or adapt it to the admin endpoints, e.g. groups via the Admin API, if you want tenant-wide coverage without workspace membership), and send the result to a table or Teams alert on a schedule.

To stop the number growing, change how reports land in that workspace: since service-created reports did not hit the error, deploy new versions with Update Report Content / rebind (or Fabric item definition APIs / Git) instead of re-importing a .pbix each time, so you update an existing report rather than creating a new import record.

So my overall approach would be:

Scheduled script: reports + models + imports per workspace
-> Alert at ~900
-> Stop re-importing .pbix: update existing reports in place
-> Support ticket for cleanup of the existing orphaned imports

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.

Thank you for your feedback but its not practical for us to just change our approach. In other scenarios we have optimized this but in this workspace its specifically allowing clients to interact with their workspaces via Power BI Desktop and therefore we need to provide import functionality (along with other reasons)
The real point is that Microsoft cannot enforce a limit that cant be managed by the user - this is a bug (or a badly designed feature)