Skip to main content


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

Troubleshooting Paid Media Manager

Updated on September 15, 2022

Use the following troubleshooting tips to help solve issues related to Paid Media Manager configuration.

Pega Customer Decision Hub

Issue: Paid synchronization job fails with the message "Sync Job Failed with data flow errors"

If a synchronization job fails due to a data flow error, the Sync Tracking tab of the Paid Media landing page displays the message Sync Job Failed with data flow errors, as in the following figure:

To solve this issue, do the following steps:

  1. In Dev Studio, click ConfigureDecisioningData flowBatch.
  2. Look for the failed data flow and diagnose the error.
  3. After diagnosing and resolving the error cause, rerun the paid run, for example, by re-executing the segment run or outbound run, or by waiting for their next scheduled run.

Issue: Paid synchronization job fails with the message "Queue processor failed with following error"

If a synchronization job fails due to a queue processor error, the Sync Tracking tab of the Paid Media landing page displays the message Queue processor failed with following error.

To solve this issue, do the following steps:

  1. In App Studio, click SettingsChannelsPaid Media.
  2. Click the arrow by the failed synchronization job to view the error details, as in the following figure:
  3. At the bottom of the XML section, find and note down the JobID and DestinationKey, for example, PM-1001 and DK123EB.
  4. Switch to Admin Studio.
  5. Click ResourcesQueue processors.
  6. In the list of queue processors, find PaidMediaSync, and click the number in the Broken column, as in the following figure:
  7. Filter the Reference object key column by entering the concatenated JobID and DestinationKey that you noted in step 3.

    For example, if the JobID is PM-1001 and the DestinationKey is DK123EB1, enter PM-1001DK123EB1, as in the following figure:

  8. Click the More icon by the failed synchronization item to view the full error details.
    Tip:

    When analyzing the error details, look for the Caused by section at the bottom of the error log. This section should contain a message that describes the cause of the error. For example, the following error message indicates that a paid synchronization run has failed due to an expired access token for a specific Google Ads paid destination:

    Caused by: com.pega.mkt.paidmedia.sync.AudienceSyncException@42ebe857[paidMediaErrors=[com.pega.mkt.paidmedia.error.PaidMediaError@14147b5e[paidRunId=RT-176,dataFlowRunId=N/A,code=GG-AE-004,message=The access token in the request header is either invalid or has expired., severity=CRITICAL,occurredOn=Fri Nov 20 05:16:04 EST 2020,platform=Google,destination=XXX-YYY-ZZZZ,syncType=REALTIME]]]

    At the bottom of the error log you can see the following additional information to help you discover which specific paid media run is associated with the error:

    JobID
    Unique identifier of a specific paid media run.
    DestinationKey
    Unique identifier of a paid destination
    SyncType
    Type of paid run, for example, Segment, Outbound, or Real-time.
  9. After diagnosing and resolving the error cause, in App Studio, click SettingsChannelsPaid Media, and then click Retry by the failed synchronization item, as in the following figure:

Tags

Pega Customer Decision Hub 8.7 Decision Management

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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