In the API Endpoints i get no log, its just emtpy. Anyone else had this problem before?
Version 2026.2.3 running on Windows Server with integrated Webserver
c2dfa326-6d4e-4018-9e22-4389ce742ac0.png
Hello nikopieper,
Thank you for reporting this.
I understand that on PowerShell Universal 2026.2.3, running on Windows Server with the integrated web server, the Log tab for your API Endpoints remains empty.
To help narrow down what part of the endpoint logging is affected, could you please confirm the following?
* Are the API Endpoints themselves executing and returning responses successfully, with only the Log tab remaining empty?
* Does this happen with all API Endpoints or only specific ones?
* If you keep the Log tab open and invoke the endpoint several times, does it remain completely empty?
* Are you expecting to see the automatic request activity in the Log tab, messages generated with `Write-PSULog`, or both?
* Did this behavior start after upgrading to 2026.2.3? If so, what was the last PSU version where you remember the endpoint logs working correctly?
These details will help us determine whether the issue is specific to the live endpoint log view, `Write-PSULog`, or endpoint logging more generally.
Best regards,
Ruben Tapia
Hello Ruben,
* Are the API Endpoints themselves executing and returning responses successfully, with only the Log tab remaining empty?
Yes API Endpoints are working fine, just no logs.
* Does this happen with all API Endpoints or only specific ones?
With all API endpoints
* If you keep the Log tab open and invoke the endpoint several times, does it remain completely empty?
Yes its completely Emtpy
* Are you expecting to see the automatic request activity in the Log tab, messages generated with `Write-PSULog`, or both?
Nothing is shown, the load more button is disabled
* Did this behavior start after upgrading to 2026.2.3? If so, what was the last PSU version where you remember the endpoint logs working correctly?
I belive it was already not working before, but we just started realy using Endpoints.
Hello nikopieper,
Thank you for confirming those details.
We will test this behavior today using PowerShell Universal 2026.2.3 and 2026.2.4 under comparable conditions to determine whether we can reproduce the empty API Endpoint Log behavior and whether there is any difference between the two versions.
Once our reproduction is complete, if we confirm the behavior in 2026.2.3, we will proceed with the appropriate internal escalation as a defect affecting that version.
I will update this thread once the testing is complete and we have the results.
Best regards,
Ruben Tapia
Hello nikopieper,
We completed comparative testing with PowerShell Universal 2026.2.3 and 2026.2.4. In both versions, the API Endpoint executed successfully and the request activity appeared correctly in the Endpoint Log while the Log tab was open. We were therefore unable to reproduce the empty Log behavior you are seeing.
To help us compare your environment with our clean test environment, could you please check whether the same endpoint requests appear under Platform > Logging immediately after invoking the endpoint?
Please also send the following sanitized diagnostic information to me at ruben.tapia@ironmansoftware.com referencing case 55852:
* The PSU system log covering a short time window in which you reproduce the issue. Please include the approximate timestamp and time zone of the test request.
* The relevant logging settings from `appsettings.json`, including `SystemLogLevel` and `SystemLogPath` if configured. Please do not send the complete file.
* If you have logging settings configured in `settings.ps1`, please include only the relevant logging-related lines.
* Please confirm whether the behavior is the same when accessing the Endpoint Log with an account assigned Administrator role.
Please sanitize these files before sending them. Remove credentials, tokens, license keys, cookies, private keys, connection strings, email addresses, usernames, customer data, tenant or account identifiers, internal domains, hostnames, IP addresses, and private URLs.
These details should allow us to determine whether the API log entries are being generated and persisted but not displayed in the endpoint-specific Log view, or whether they are being filtered earlier in the logging pipeline.
Best regards,
Ruben Tapia