Hello.
In a recent incident where the getnba was not writing in the IH table, we had a webex session with a PEGA expert and discovered that the MKTResponseHandler dataflow was stopped.
Once it was started again, everything worked fine. But the problem is that despite several people checking all the known dataflows of our application, we couldn’t find any single one stopped. This especific dataflow is an out-of-the-box dataflow that we have no information about and it apparently is extremely important.
We also searched in the support knowledge base but couldn’t find any more info.
Would it be possible for someone to give us more information about this dataflow? We need to know when ir can potentially be stopped automatically so we can prepare for ir.
Thanks and regards.
@GuillermoR0511 Two support ticket - which one is the correct one?
- INC-B4252 (ProcessResponseStream Data flow Unavailability Issue)?
Issue: MKTResponseHandler dataflow failed and stopped at 16:07 on 10-Jan Solution: DB issue that stopped the dataflow run.
- INC-B16093 (The service URL JVMMetrics does not start with a host name/not writing to IH tables)
Issue : CDHResponseSource Dataflow was on stopped state that’s why no records are going to IH. Solution by @roya2_gcs : Restarting CDHResponseSource DF resolved issue.
I’m unable to find any documentation apart from Creating a real-time container and Capturing responses to actions triggered by a real-time container. ( ResponseCapture was the original data flow run name. It was renamed as MKTResponseHandler in 2019. The MKTResponseHandler instance is available in Data-Decision-DDF-RunOptions. From the real time data flow landing page , New option created the data flow and in that checked the Managed data flow option by configuring the ruleset . This created an instance of Data-Decision-DDF-RunOptions. From 8.4 on the email response handling is managed through a data flow run which is named as MKTResponseHandler.
Usually the suggestion is to check for this Realtime DF under Pega-DM-DDF-Work instances
It used to be documented in a guide called 'Troubleshooting-actions-and-flows’. but that link is broken.
@roya2_gcs are you able to provide any more details about this dataflow?
@MarijeSchillern the incident I reference is the INC-B16093. We are afraid of this dataflow stopping randomly because we don’t understand how it works or have any info regarding it.
@GuillermoR0511 thanks.
I will check internally, but all I can find is that the CDH Product team sometimes work with clients to refactor CaptureResponse flow to capture by channel approach instead of Implicit Impression capture.
More details refer: Pegasystems Documentation
@AmyRohe are you able to provide any input here?