Skip to main content
Close announcements banner

Error handling

Qlik Replicate handles different types of errors during its operation. The way the system should respond to these errors depends on several aspects, including the component where the error occurred, the type of error, and the scope of the error. Because different sites may have different requirements for error behavior, Qlik Replicate lets you configure the error handling.

You can also add an environment variable that instructs Replicate to create dump files in the event of a crash. The dump files can then be used by Qlik Support to troubleshoot the cause of the crash. For more information, see Creating Dump Files.

You can determine whether or not to override the global error handling settings. For more information, see Error Handling Settings.

Information note

The option to set a Global Error Handling policy is not available when the Apply batched changes to multiple tables concurrently option is selected in the Task Settings' Change Processing Tuning tab.

Clicking the Error Handling tab in the Task Settings window reveals the following sub-tabs:

  • Environmental Errors: An error that is caused by an environmental problem in the source or target endpoint or on the network. Some examples of environmental errors are loss of communication with the source or target endpoint, restarting a database, or network problems.
  • Data Errors: An error related to data processing at the record level. Some examples of data errors are conversion errors, errors in transformations, or bad data.
  • Table Errors: An error in processing data or metadata for a specific table. This only includes general table data and not an error that relates to a specific record.
  • Apply Conflicts: Errors that occur when the target endpoint is not synchronized with the source endpoint when processing changes.

    This can cause duplicate key errors on INSERT operations or zero rows affected on UPDATE/DELETE operations.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!