Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

OperationTimedOutException when Paid Media Campaign is run



Running a Paid Media Campaign fails with OperationTimedOutException at the data flow stage.

Error Messages

Caused by: com.datastax.driver.core.exceptions.OperationTimedOutException: Timed out waiting for server response at com.datastax.driver.core.exceptions.OperationTimedOutException.copy( at com.datastax.driver.core.exceptions.OperationTimedOutException.copy( at com.datastax.driver.core.DriverThrowables.propagateCause( at com.datastax.driver.core.AbstractSession.prepare( at com.pega.dsm.dnode.impl.dataset.cassandra.SessionProxy$PreparedStatementProxy.statement( at com.pega.dsm.dnode.impl.dataset.cassandra.SessionProxy$PreparedStatementProxy.getVariables( at com.datastax.driver.core.BoundStatement.( at com.pega.dsm.dnode.impl.dataset.cassandra.statement.RequestorAwareBoundStatement.( at com.pega.dsm.dnode.impl.dataset.cassandra.SessionProxy.createBoundStatement( at com.pega.dsm.dnode.impl.dataset.cassandra.CassandraSaveWithTTLOperation.createBoundStatement( at com.pega.dsm.dnode.impl.dataset.cassandra.CassandraSaveWithTTLOperation$InsertStatementGenerator.createStatement( at com.pega.dsm.dnode.impl.dataset.cassandra.CassandraSaveWithTTLOperation$4.emit( ... 47 more Caused by: com.datastax.driver.core.exceptions.OperationTimedOutException: Timed out waiting for server response at com.datastax.driver.core.RequestHandler$SpeculativeExecution.onTimeout( at com.datastax.driver.core.Connection$ResponseHandler$ at io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire( at io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts( at io.netty.util.HashedWheelTimer$ at io.netty.util.concurrent.DefaultThreadFactory$ at

Steps to Reproduce

  1. Launch the application
  2. Configure a Paid Media Campaign
  3. Run the campaign

Root Cause

A defect in Pegasystems’ code or rules.


  1. Apply HFix-42302
  2. Modify Dynamic System Settings 'dataflow/paidmedia/customerBatchSize' from 2000 to 8000 to reduce the network round trips


Published July 23, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us