Troubleshooting Paid Media Manager
Use the following troubleshooting tips to help solve issues related to Paid Media Manager configuration.
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:
- In Dev Studio, click .
- Look for the failed data flow and diagnose the error.
- 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:
- In App Studio, click .
- Click the arrow by the failed synchronization job to view the error details, as in the
following figure:
- At the bottom of the XML section, find and note down the JobID and DestinationKey, for example, PM-1001 and DK123EB.
- Switch to Admin Studio.
- Click .
- In the list of queue processors, find PaidMediaSync, and click the number in the
Broken column, as in the following figure:
- 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:
- 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: [email protected][paidMediaErrors=[[email protected][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.
- After diagnosing and resolving the error cause, in App Studio, click , and then click Retry by the failed synchronization
item, as in the following figure:
Previous topic Troubleshooting output templates Next topic Troubleshooting real-time events