In Qlik Replicate, the "Apply Exceptions" feature captures records that fail to be applied to the target endpoint due to errors (e.g., data constraint violations). These failed records are stored in a dedicated control table, typically named attrepapplyexceptions, on the target database. By default, Qlik Replicate is configured to retain these exception records indefinitely. This ensures that no data is lost and allows administrators ample time to investigate, correct, and reapply the failed transactions without a risk of automatic deletion. This default behavior can be overridden in the task's Error Handling settings.

B. 7 days: This is a configurable retention period, but it is not the default setting for Apply Exceptions.

C. 60 days: This is a possible custom value for data retention, not the out-of-the-box default for this specific feature.

D. 30 days: While a common retention period for logs or other temporary data, it is not the default for Apply Exceptions.

1. Qlik Replicate User Guide (May 2024): In the section "Defining advanced error handling settings," under the "Store changes" tab, the setting "Delete exceptions older than (days)" is described. The documentation implicitly confirms the default is indefinite by not having a default numerical value checked or pre-filled, requiring the user to explicitly enable and set a time limit. The default state is to not delete. (Reference path: User Guide -> Setting up a replication task -> Using the Replicate Console -> Defining and managing tasks -> Defining advanced error handling settings -> The Store changes tab).

2. Qlik Replicate User Guide (May 2024): The section "Managing Apply Exceptions" describes the attrepapplyexceptions table and the process for reloading or deleting records. The entire process is manual by default, reinforcing that automatic deletion is not the standard behavior. (Reference path: User Guide -> Monitoring tasks -> Managing Apply Exceptions).