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

Records are stuck in the MKT_Staging table

SA-67199

Summary



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. 


Error Messages


Not Applicable


Steps to Reproduce

  1. 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
  2. Select the Write to DB option. The offer must have a loop which triggers the list of profiles of a single customer
  3. Trigger the event


Root Cause



The database staging table does not support writing multiple records for a given Subject + Offer + Treatment as per the Pega design keys. 

Resolution



Apply HFix-47252.
 
Suggest Edit

Published August 19, 2019 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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