V4 to v5 upgrade - missing endpoint docs

PowerShell Universal
1 
Product: PowerShell Universal
Version: 5.6.6

I’m working through an upgrade from ~v4.3 to v5.6 and hit some issues. I’m hosting on IIS (“nested application”), using Windows auth and “strict” security model. I installed the dotnet 9 bundle and made the necessary changes to align with v5 environments.

Since the first upgrade to v5, none of my endpoints show up in swagger. I can see the page in swagger, and it shows the schemas, but none of the endpoints. “No operations defined in spec!”

I see the following error repeated in system logs:

[ERR][PowerShellUniversal.TimedHostedService] An error occurred running the scheduled job.
Microsoft.EntityFrameworkCore.DbUpdateConcurrencyException: The database operation was expected to affect 1 row(s), but actually affected 0 row(s);
2

I performed the following test.

I create new documentation:

New-PSUEndpointDocumentation -Name "eptest" -Authentication -Definition {} -Url "/api/eptest"

I create two endpoints:

New-PSUEndpoint -Url "/api/eptest/one" -Method @('GET') -Authentication -Path "..\eptest\one.ps1" -Documentation "eptest" 
New-PSUEndpoint -Url "/api/eptest/two" -Method @('GET') -Authentication -Role @('Operator') -Path "..\eptest\two.ps1" -Documentation "eptest"

I can immediately see the swagger page with both new endpoints. I “reload all” config files from admin console. I still see both endpoints. I recycle the IIS application pool, and then I only see the first endpoint in the docs.

This behavior does seem to be reproducible. It suggests that the problem is associated to the role assignment in the second endpoint. Am I doing that incorrectly? I currently assign roles (mapped to AD group claims) to all endpoints.