For Each Mail (365) throws :'For Each Email' with ID 5 threw or propagated an exception while being canceled when using a time or 365 connector trigger but works well triggering manually

[Bellian]

Hello, I am using for mail each activity , i cant seem to understand this error : The activity ‘For Each Email’ with ID 5 threw or propagated an exception while being canceled
This happens once published to orchestrator and triggered by time or a connector365 but when i run it manually using assistant it does not throw that error
please assist

[ashokkarale]

Welcome to the Community @Bellian.

It’s actually hard to recreate this issue but in past one user reported this issue. According to that it was in Finally section of the Try Catch.

System exception.The activity 'Try Catch' with ID 21 threw or propagated an exception while being canceled.?

hello, i’m using the REFramework in my project and i get the error below when i run it in the orchestrator, what this error means? [image]

In your code, try to set logs and identify exact activity that is failing. Something is not being intialized could be the reason here.

[prashant1603765 (Prashant Kumar)]

Hi @Bellian

Use the try catch or check and increase job timeout, ensure stable mail connection, add error handling around the For Each Email activity, and add logging to identify where it fails.

[Shwetha_Ningappa]

@Bellian please try the below steps

• Check timeout/kill settings in the trigger — it might be auto-terminating the job.
• Add Try-Catch around the For Each Email loop to handle graceful cancellation.
• Check unattended robot permissions for Outlook or 365 connection.
• Add logs before and after the loop to trace the cancel point.

[Bellian]

@Shwetha_Ningappa , @ashokkarale, could not resolve this

[ashokkarale]

@Bellian,

Are you able to find out exactly activity which is causing this issue?

[Bellian]

When running either in debug mode or using assistant, there’s no error only when triggered from orchestrator that’s where it occurs

[Shwetha_Ningappa]

@Shwetha_Ningappa

• Check timeout/kill settings in the trigger — it might be auto-terminating the job.
• Add Try-Catch around the For Each Email loop to handle graceful cancellation.
• Check unattended robot permissions for Outlook or 365 connection.
• Add logs before and after the loop to trace the cancel point.

Can you please elaborate the error, what is the issue you are getting with screenshot,that may help us to debug

[ashokkarale]

@Bellian is it occurring right on the For Each Email activity ?

[sonaliaggarwal47 (Sonali Aggarwal)]

Hi @Bellian

I see you have for each email defined under try block. Could you please confirm if your exception is being caught by catch block?

[Bellian]

Yes

The activity ‘For Each Email’ with ID 6 threw or propagated an exception while being canceled.

at UiPath.Executor.BaseRunner.EndExecute(IAsyncResult result)
at UiPath.Executor.InProcessRunner.EndExecute(IAsyncResult result)
at UiPath.Core.Activities.ExecutorInvokeActivity.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)

[ashokkarale]

@Bellian,

Can you try recreating/replacing the workflow or activity. There seems something misconfigured or broken.