2026.3.3.0 - Error with Set-PSUCache
I have a script which loads various items into the PSU Cache. One is a csv that's 7,158kb, and has always succeeded.
Now with 2026.3.3.0, I get this error. I don't know if there's a setting that could be adjusted (couldn't find one in app.config).:
08:33:02.176
ERROR
Status(StatusCode="Unknown", Detail="Exception was thrown by handler. BadHttpRequestException: Request body too large. The max request body size is 30000000 bytes.", DebugException="Grpc.Core.Internal.CoreErrorDetailException: {"created":"@1791293582.012000000","description":"Error received from peer ipv6:[::1]:64789","file":"..\..\..\src\core\lib\surface\call.cc","file_line":953,"grpc_message":"Exception was thrown by handler. BadHttpRequestException: Request body too large. The max request body size is 30000000 bytes.","grpc_status":2}")
All Comments (4)
Hello @mshepard70
Thank you for reporting this.
The error indicates that the request generated by Set-PSUCache is exceeding the 30,000,000 byte request body limit. The CSV file size on disk does not necessarily represent the final request size because the imported PowerShell objects must be serialized before they are sent.
To determine whether this is a regression in 2026.3.3.0, could you please provide:
• The exact PSU version where the same script and dataset last worked successfully.
• A minimal sanitized example showing how the CSV is imported and how Set-PSUCache is called.
• Whether you are using parameters such as -Persist or -Integrated.
• Whether this is affecting a production environment and whether you currently have a workaround.
Please do not upload the CSV itself. Once we have the previous working version and the command structure, we can determine the most appropriate comparison and reproduction path.
I also reviewed the current 2026.3.3.0 release notes and did not find a documented change specifically related to Set-PSUCache request size limits.
Because this is a public forum, please sanitize all evidence before posting. Remove credentials, tokens, license keys, cookies, private keys, full connection strings, email addresses, usernames, customer data, tenant or account identifiers, internal domains, hostnames, IP addresses, and private URLs. Please do not upload unredacted HAR files, memory dumps, database backups, or complete configuration files to this public thread.
References:
https://devolutions.net/powershell-universal/release-notes/
Best regards,
Ruben Tapia
It's failing in a dev environment on 2026.3.3. Production is still on 2026.2.1 and it's succeeding there.
the sanitized code is this:
Set-PSUCache -Key CacheKey -value (Import-csv "<PATH TO CSV>") -Integrated
@mshepard70 I'll open an issue for this. We likely need to adjust the max size but I don't know if there is a workaround. I will circle back if I find one.
Adam Driscoll
PowerShell Expert and Software Architect at Devolutions
Echoing this, I had to downgrade back to 2.5. No version 3 was working. I'm using the cache to store some fairly large tables.