About the "Continue on error" property

1. About the "Continue on Error" Option

Behavior When "Continue on Error" is Set to False

The "Continue on Error" property is set to False by default. When an error occurs under this setting, an error log is generated and the process is halted.

Behavior When "Continue on Error" is Set to True

There may be situations where you want the process to continue even if an error occurs. In this case, setting "Continue on Error" to True allows the workflow to continue despite errors. However, error logs are not generated in this scenario.

Example: Deleting a File

Consider a workflow where you attempt to delete the " Afternoon_Run-4" file. If the file does not exist in the project folder, an error will occur when the "Delete" activity is executed.

• When "Continue on Error" is False: An error log is generated, and the subsequent "Message Box" activity is not executed. The process is terminated as shown below.
  
  
  
• When "Continue on Error" is True: The process does not halt at the "Delete" activity and proceeds to execute the subsequent "Message Box" activity. 

However, no error log is generated.

2. Logging Errors While Continuing the Process

If you want the process to continue after an error occurs but still log the error, you can use a Try Catch activity. By placing a "Log Message" activity in the Catch block, you can log the error and continue with the subsequent activities. For more information on how to use the "Try Catch" activity, please refer to the article "Try Catch."

Here is an example of how to set this up:

1. Try Block: Place the activities that may generate errors.
2. Catch Block: Add a "Log Message" activity to log the error.
3. Finally Block (Optional): Add any cleanup activities if needed.

By using this approach, you ensure that errors are logged while allowing the workflow to continue.

For more details on using the "Try Catch" activity, refer to the article Try Catch.