Records are stuck in the MKT_Staging table
A loop is configured in an offer flow to iterate over the number of devices a customer holds and send push notifications to each of them. Every time the loop runs, RANKID is incremented by 1 (RANKID = RANKID + 1). When the user triggers the offer through the Real Time event and saves the records to the database table using Write to table in the offer, the records get stuck in the MKT_Staging table.
Steps to Reproduce
- Design a flow to trigger the offer via Real time event. The offer flow must have a looping mechanism to send out multiple Push Notifications
- Select the Write to DB option. The offer must have a loop which triggers the list of profiles of a single customer
- Trigger the event
The database staging table does not support writing multiple records for a given Subject + Offer + Treatment as per the Pega design keys.
Published August 19, 2019 - Updated December 2, 2021
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.