document-understanding
2024.10
true

Document Understanding Release Notes
Last updated Oct 22, 2025
Release date: September 24, 2025
- Fixed an issue where deployments would be scheduled on CPU nodes instead of GPU nodes. The service would continue to run on CPU, but performance was degraded.
- Fixed a compatibility issue that caused the CORS validation job to fail when using certain S3-compatible storage providers. Document Understanding now supports these environments by making checksum enforcement configurable and disabled by default.
Erratum - added October 22, 2025: If you enable automatic certificate rotation
using the command
uipathctl config token-signing-certificates
automatic-key-management
, you must then manually restart Document
Understanding pods every 14 days.
This beahvior occurs because Automation Suite manages the lifecycle of signing keys when automatic certificate rotation is active. This process includes rotating keys every 90 days and announcing new keys 14 days prior to rotation. Old keys are retained for 14 days post-rotation, and after which they are deleted.
As a workaround, you can manually restart deployments using the following
commands:
kubectl -n uipath rollout restart deploy
kubectl -n uipath rollout restart sts
kubectl -n uipath rollout restart deploy
kubectl -n uipath rollout restart sts
As an alternative, disable automatic rotation until a fix is released, using the following command:
uipathctl config token-signing-certificates automatic-key-management disable
uipathctl config token-signing-certificates automatic-key-management disable