Users with excel workflows accessing large amounts of data will encounter this error "Job stopped with an unexpected exit code: 0xE0434352", from time to time.
Follow the below steps:
- Stop excel workflow temporarily and run a different workflow to see if the error still occurs.
- Make simple excel workflow that just accesses the data in the same way to see if error still occurs.
- Use kill excel Com object before reading excel object.
- Use retry scope or increase the timeout to 60-90 seconds to ensure these errors are reduced.
- Update to the latest excel activities package.
- Open task manager while the process is running and see if there are other memory intensive processes running. If so, close them and see if that makes the error go away.
In order to avoid memory leaks and out of memory exception. Below are some of the best practices to be followed:
- The size of the xaml should not be more than 1 MB .
- Split the workflows in smaller parts, and call them in invoke workflow
- If you are using Invoke workflow , try to keep "isolated" property checked .
- Do not pass data tables as arguments. Instead of that , write out the information to a temporary excel sheet, and read it again from the XAML where you intend to use it for further processing.
- Clear data tables, when they are not in use anymore, if you have used any.
- If you are trying to read a large excel file , please break down reading into small chunks of file (not more than 5000 records).
- Dispose of other variables when not in use (Refer the link to dispose objects)