ZTA 2.3.0 completes successfully with clean export/database/test logs, but generated HTML report crashes when renderering

[saulov8]

ZeroTrustAssessment 2.3.0 completes successfully with clean export, database, and test progress logs, but the generated HTML report crashes when rendering in the browser.

The assessment appears to complete successfully. The export phase completes with no failed jobs, the database phase completes successfully, and the test phase shows all tests completing with Pass results. However, when opening ZeroTrustAssessmentReport.html, the report fails to render and displays an unexpected application error.

An older Zero Trust Assessment report generated a few months ago still opens successfully in the same browser on the same machine.

[astaykov]

Could you, please, confirm if you see the same issue with https://www.powershellgallery.com/packages/ZeroTrustAssessment/2.2.58-preview version?

[saulov8]

Thanks @astaykov, I will test ZTA 2.2.58 preview.

I am currently running ZTA 2.3.0. I also tested a different tenant using the same machine, same browser, and same ZTA 2.3.0 module, and that report rendered successfully. So, the issue appears specific to the affected tenant/report output rather than the local environment.

[saulov8]

@astaykov same issue with ZTA 2.2.58, it must something specific with that tenant

[saulov8]

Claude helped me to find a potential bug. After inspecting the HTML, the cause is Sankey link objects where value is null or 0. D3's Sankey renderer can't handle non-positive values and crashes. The affected tenant had 10 null and 14 zero values, likely because Graph returned no data for certain paths due to tenant-specific data gaps (it appears to have come from tenant's sign-in logs or device compliance data).

Claude ran run this workaround:

$html = Get-Content "ZeroTrustAssessmentReport.html" -Raw
$html = $html -replace '"value":\s*null', '"value": 1'
$html = $html -replace '"value":\s*0', '"value": 1'
$html | Out-File "ZeroTrustAssessmentReport_fixed.html" -Encoding UTF8

The report rendered just fine after running the workaround.

[astaykov]

awesome!
thanks digging this down.
We will try to reproduce the issue and provide a fix.
please do not close this issue to keep tracking.

[astaykov]

@saulov8 can you check with latest preview release if the issue is fixed?

 Install-Module -Name ZeroTrustAssessment -AllowPrerelease

When running it should show v2.3.1-preview version.