Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Error and Warning Handling

Updated on August 4, 2022

The Next-Best-Action Designer displays errors and warnings resulting from each scheduled and real-time paid run. Errors and warnings are displayed chronologically for the Next-Best-Action hierarchy level and paid destination on which they occurred.

Pega Customer Decision Hub

If multiple errors are generated for the same destination, they are added to the existing work object. Paid Media Manager maintains a history of errors and warnings, as well as information about the number of records affected.

Errors that occur during Segment-based runs are logged as work objects of the type PegaMKT-Work-PaidSync. The paid sync errors are displayed in the Paid Sync tab of the Segment for which they were recorded.

If an error occurs, confirm that your account in the integrated platform is properly configured and activated, then resolve the error work object before triggering another paid run.

Errors displayed in the Next-Best-Action Designer come directly from the integrated external system. If you cannot resolve the problem yourself, contact the product team for your advertising platform.

To generate Paid Notification work objects, update the following Data transform rules:

  • Data-Party-Operator – MarketingAdministrator

  • Data-Party-Operator – MarketingAnalyst

For both rules, set the property pyWorkPartyUri to the operator ID used by your administrator and analyst.

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us