Faulted Job: Job stopped with an unexpected exit code: 0xE0434352

Help Robot
1

I have a job that is triggered Friday night and runs until Sunday night.

Sometimes it end with status Faulted.This should be impossible, since I’m using the REFramework. When I look into the Job Details, it just says “Info: Job stopped with an unexpected exit code: 0xE0434352”. I don’t know why this keeps happening.

When i look into the logs, it doesn’t end with any logs of level Error or Fatal or even a Warning. It seems like the execution just randomly stops.

image
image1633×782 99.8 KB

This happened after 10 hours, and a transactions only takes 35 seconds to complete, so the flow definetely works in normal cases.

The error prevents the job from running through the whole weekend.

Can anyone help me out please?

1 Like
2

Hi @razvan.chiose ,
Was it working fine before?
Can you share infor about version Studio, package,…
regards,

4

Probably best to validate your infrastructure,

  • does the event log in the orchestrator mention anything on connection interruptions between the robot client and the orchestrator.
  • is there scheduled maintenance on one of the components? Such as a client or server restart at night.
5

It only ran for long periods of time a couple of times, so I can’t say if it was “working fine before”.

As for the versions, I’m on 2023.4.1 and these packages:

image
image1169×749 51 KB

6

Hi @razvan.chiose,

If a Job Runs More than 24 hours It will Automatically Faulted.

Cheers

7

Ok, good to know but my job didn’t even get to 12 hours.

8

Hey,

Can you delete all excel processes from task Manager first and then run your workflow and if still doesn’t work may be the file is corrupted or Large Amount of Data in Excel So copy the same file information in another excel and then run and see if you are still receiving the error.

Cheers

9

The only usage of Excel files is when the REFramework reads the config file (which is definetely not that big). Microsoft Excel is not even installed (the Excel reading is done using the workbook activity that doesn’t need the Excel app installed) so there are no processes to in the Task Manager.

10

I never got an alert that Orchestrator lost connection with the robot on this tenant.

There was no maintenance, I have files left open on that machine from a week ago.

11

@razvan.chiose

Try troubleshooting using below details

  1. Check the usage of your cpu during the process may be use logs and check it
  2. Check the event viewer logs at the time
    Job is faulted
  3. Check if there is any scheduled maintaining at that point
  4. Check if the screeen locks or so are disabled or not
  5. Is it failing after any specific log always? Or is it random

Cheers

12

Having the job split in two seems to have helped. Now, instead of a Trigger that is scheduled to stop the job after 24 hours, I have two triggers as follows:

  1. First trigger starts a job at 12:00AM and is scheduled to stop after 11h 40minutes.
  2. 20 minute break to let the machine “cool down”.
  3. Second trigger starts a job at 12:00PM and is scheduled to stop after 11h 40minutes.

My general feeling is that the machine was running out of resources at random times. This seems to have solved the issue for now. Will keep replying here if I discover anything new.

1 Like
13

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.