Job Stuck in Running State, Logs Say 'Execution Suspended'

Help Document Understanding
1

I am seeing a document understanding performer stuck in ‘Running’ state, despite the logs showing that the action is created and the execution suspended.

If I kill the job, it gets stuck in terminating. We then have to restart the machine to allow the job to end, however the same issue keeps re-occurring.

The orchestrator is on-prem, so we are currently checking space to rule out server space issue.

MicrosoftTeams-image (6)
MicrosoftTeams-image (6)1410×576 186 KB

2

@Olivia_Minshall

Are you using any wait for resume task?

cheers

3

We have the wait for external task and resume - so the process is just adding an action and suspend.

4

@Olivia_Minshall

So thats the functionality right…It gets suspended till its completed

image
image1060×143 19.3 KB

cheers

5

Yes, unfortunately though the job actually stays in ‘Running’ state, and does not change to ‘Suspended’ as you would expect.

We believe that it is due to a capacity issue, after we failed to be able to upload a new package as well.

6

Hi,

Just wanted to see if this got resolved?

I remember having the same issue with one of our clients, and as expected, it was related to network delays, and some database capacity issue. Could be a similar cause in yours too…

Let know if you still hsve the issue

7

Hi,
It is suspended for the Human verification(Action center).

kindly look at action center in your orchestrator, the file need to be verified
after you verified only it will continue to work

8

There can be several reasons why a UiPath Document Understanding performer is stuck in a “Running” state despite the logs showing that the action is created and the execution suspended.

  1. Insufficient server resources: As you have mentioned, the orchestrator is on-prem, one of the possible reason could be low memory or disk space on the server which can cause the job to get stuck.
  2. Concurrent jobs: Another possible reason is that there are too many concurrent jobs running on the server, which can cause the job to get stuck.
  3. Network connectivity issues: If there are network connectivity issues between the UiPath Document Understanding performer and the server, this can cause the job to get stuck.
  4. Incorrect configuration: Another possible reason is that the UiPath Document Understanding performer is not configured correctly, which can cause the job to get stuck.
  5. Corrupted files: Another possibility is that the files or data being processed by the UiPath Document Understanding performer are corrupted and causing the job to get stuck.

To fix this issue, you should check your server resources, review the number of concurrent jobs running, check your network connectivity and make sure that the performer is configured correctly.

Also, you can try to stop and restart the performer, if the problem persists, you may want to contact UiPath support for further assistance.