Regarding the setting "Store trace/verbose logging in memory, but if any error occurs write to the logs"

iti-attunity-sup — Mon, 20 Apr 2026 09:54:10 GMT

Hello Support Team,

I hope you are doing well.

I would like to clarify a few points as we were unable to verify the behavior internally.

If an error is output while this setting is active, but the task continues to run:

Do we need to manually lower the log level back to its original state?
Or, in the case of a transient error, will the log level automatically revert to the original setting once the error is resolved?

Best Regards.

Re: Regarding the setting "Store trace/verbose logging in memory, but if any error occurs write to the logs"

SachinB — Mon, 20 Apr 2026 10:07:42 GMT

Hello @iti-attunity-sup

Qlik Replicate allows you to capture detailed Trace or Verbose logs in a memory buffer rather than writing them continuously to disk. This feature, often called conditional logging, is designed to troubleshoot unpredictable errors without the performance overhead and disk space consumption of constant high-level logging

When the logging level is set to "Trace" or "Verbose", you can instruct Replicate to store the logging information in memory until an error occurs. On detecting an error, Replicate will begin writing to the physical logs and continue to do so for a few minutes after the initial occurrence of the error.

If no error occurs before the allocated memory is used up, Replicate will empty the memory buffer and start afresh.

This option is useful for tasks that fail unpredictably and for no obvious reason. The problem with continually writing large amounts of information to the logs is twofold:

Running in "Trace" or "Verbose" logging mode will quickly use up available disk space (unless the logging settings have been configured to prevent this).
Continually writing large amounts of data to the logs will affect performance.

No, you do not need to manually lower the log level after an error is resolved. The setting is designed to stay active in the background, continuously buffering trace or verbose data in memory without writing it to disk unless another error occurs. You only need to manually change it if you want to stop collecting detailed diagnostics altogether

Yes. When a transient error is detected, Replicate automatically flushes the memory buffer to the physical log file. It then continues writing detailed logs directly to disk for a few minutes following the initial error. After this brief period, the system automatically reverts to its original state, once again storing the trace/verbose information in memory rather than writing it to disk

Please refer the below link for more information

Qlik-Replicate-How-to-store-trace-and-verbose-logging-in-memory

tasks_loggingSettings

Regards,

Sachin B

topic Regarding the setting "Store trace/verbose logging in memory, but if any error occurs write to the logs" in Qlik Replicate

Regarding the setting "Store trace/verbose logging in memory, but if any error occurs write to the logs"

Re: Regarding the setting "Store trace/verbose logging in memory, but if any error occurs write to the logs"