Document Understanding Release Notes

DELIVERY:

Last updated Oct 22, 2025

2024.10.4

Release date: 26 June 2025

Minor improvements

We're constantly working to improve your UiPath Document Understanding experience. This release brings security improvements and accessibility fixes to stabilize the behavior for some of the available features presented in Document Understanding modern projects.

Known issues

In environments where Workload Identity is enabled, SQL connections may fail on initial pod startup. This results in an error when initiating an import job in Document Understanding modern projects.
If you are installing or upgrading your Automation Suite environment with Document Understanding modern projects enabled, check the pod logs for SQL connection errors. If any pods show SQL connection failures, restart those pods to resolve the issue. Once the connection is restored, reimport the documents. The import job should then complete successfully.
Erratum - added October 17, 2025: Service deployments may occasionally be scheduled on CPU nodes rather than GPU nodes. While the services still function on CPU, performance is significantly degraded compared to GPU execution. As a workaround, you must manually configure the resource requests and limits in Argo for the du-aimodelhost-2404 objects as follows:
```
resources:
  limits:
    cpu: '4'
    memory: 22Gi
    nvidia.com/gpu: '1'
  requests:
    cpu: '1'
    memory: 10Gi
    nvidia.com/gpu: '1'resources:
  limits:
    cpu: '4'
    memory: 22Gi
    nvidia.com/gpu: '1'
  requests:
    cpu: '1'
    memory: 10Gi
    nvidia.com/gpu: '1'
```
This issue is fixed in version 2024.10.5.
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 stskubectl -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 disableuipathctl config token-signing-certificates automatic-key-management disable
```

On this page

Minor improvements
Known issues

Was this page helpful?

PREVIOUS2024.10.3

NEXT2024.10.5

Support and Services

Get The Help You Need

UiPath Academy

Learning RPA - Automation Courses

UiPath Forum

UiPath Community Forum

Trust and Security

Cookies Policy