@SwapnilC16910701

pzPersistResults is an internal flag that tells DF_ProcessOffer whether to write the selected actions to Interaction History; if it goes false, the flow filters them out, so everything looks “dropped.” It typically flips to false when you call a container in preview/simulation mode (Customer Profile Viewer, Strategy Tester, NBA Simulator) because those runs don’t persist. It also goes false for inbound containers if the channel or container isn’t set to track impressions/outcomes, or when the caller explicitly sends persistResults=false in the container API request. Less common causes: the IH data set is disabled/misconfigured, the proposition keys are missing (so Pega refuses to persist), or you’re using a non-production Access Group that suppresses persistence. Fixes: invoke the real-time container (not preview), enable “track/persist impressions” on the channel/container, ensure the API payload does not disable persistence, confirm the IH data set and class mapping are running and healthy, and verify your offer flow or arbitration doesn’t remove write-to-IH. In short, run a real container call with tracking on, and pzPersistResults will stay true.