"transactional apply" mode is not supported, but task is in batch apply

[LaCools]

Since a few weeks, we're getting this error frequently: 

The task however is in batch apply. There is no further information in the logging. 

source is Oracle cdc, using logstream

target is databricks lakehouse (delta)

How to resolve this recurring issue?

[narendersarva]

Hello @LaCools 

This is not an issue. Replicate doesn't support Transactional apply change processing mode for Databricks endpoint. please see below user guide limitations.

"The Transactional apply Change Processing mode is not supported."

Limitations and considerations | Qlik Replicate Help

Hope this helps!

Thanks
Naren

[LaCools]

Hi @narendersarva ,

I know, that's the point. Everything is configured 'batch apply'. Yet we have tables getting suspended for this limitation while the task is batch applying. 

[SachinB]

Hello @LaCools 

Could you please provide more detailed logs or create a support case? We would like to review the complete logs to understand why Replicate is switching to one-by-one mode even though it is configured for Batch Optimized Apply.

Typically, Replicate switches to transaction (one-by-one) apply mode only when a batch operation fails. Reviewing the full logs will help us identify the exact cause.

Regards,

Sachin B

[LaCools]

Hello @SachinB 

I've created a support case 00439429. 

FYI: in this task, that's all the logs we get. In another task to a different endpoint, we get:

-failed to execute delete statement

-failed to execute update

[SachinB]

Hello @LaCools ,

Thank you for creating the support case. The respective regional TSE will review it and guide you further.

However, we noticed that the task is failing with a "Query Timeout" error on the Databricks side while deleting the batch. As a result, the task is switching from Batch Optimized Apply mode to Transaction (one-by-one) Apply mode.

Error :

++++++++++++++++++++
00011868: 2026-03-09T18:13:00 [TARGET_APPLY ]E: RetCode: SQL_ERROR SqlState: HYT00 NativeError: 0 Message: [Microsoft][ODBC Driver 18 for SQL Server]Query timeout expired [1022502] (ar_odbc_stmt.c:2858)
+++++++++++++++++++++

To address this, could you please update the following internal parameters to 10x their current values and then resume the task?

• loadTimeout: 1200

• executeTimeout: 12000

Please let us know once the changes are made so we can continue monitoring the behavior. Thank you.

Regards,
Sachin B