Reports returning with a job status of FAILED

[ga...@staq.com]

Network code: 43459271

Reports were succeeding on a daily basis until around Sept 10. All report jobs have failed since then.

I've attached our VCR tape with detailed SOAP request and response logs.

[ga...@staq.com]

Correction, sorry. The reports have been failing since Sept 19.

[Sreelakshmi Sasidharan (DFP API Team)]

Hi Gary, 

I tried a sample report against your network with the same report parameters and it succeeded without any issues. Are your reports still failing? 

Thanks,

Sreelakshmi Sasidharan

DFP API Team

[Donovan McMurray (DFP API Team)]

Hi, Gary.

We are currently investigating this issue. I'll be monitoring the progress and will report back here when it's fixed.

The issue seems to be with the custom fields that are set on your report query. I was able to run the same report successfully in the DFP UI without the custom fields.

Thanks,

Donovan McMurray, DFP API Team

[Selene Solis]

Hi Donovan,
Do you have any update regarding this issue?  because I have the same issue when I request any AD_EXCHANGE_ metric (it started on Oct. 9)

[Donovan McMurray (DFP API Team)]

Hi, Selene.

The original issue where Custom Field Ids are causing reports to fail is still being looked into by our engineers. I just checked, and I can confirm that the original request is failing with customFieldIds, but it succeeds when customFieldIds are removed. This request has several AD_EXCHANGE_ metrics and succeeds, so I think your issue is unrelated.

Please open a new topic in the DFP API Forum documenting the behavior you are seeing. Also, including your SOAP logs will help us get to the cause of your issue.

Thanks,

Donovan McMurray, DFP API Team

[ga...@staq.com]

Any updates on progress toward fixing the bug? Thanks!

On Wednesday, September 27, 2017 at 3:46:14 PM UTC-4, ga...@staq.com wrote:

[Donovan McMurray (DFP API Team)]

Hi, Gary.

Our engineers are actively looking into the cause of this bug, though I can't say for sure when it will be fixed. The bug is not completely straightforward to fix, and our engineers are working to ensure that they don't break something else in the process.

I'm monitoring the progress, and you can count on me to report back here as soon as the problem is resolved.

Thanks,

Donovan McMurray, DFP API Team

[Selene Solis]

Hi Donovan I don't see why I need a new topic because I'm getting the same error as is described on this thread 

I've attached the Soap log
could you provide me the Dimensions & Columns that you were able to request reports?

Regards

[Donovan McMurray (DFP API Team)]

Hi, Selene.

The original problem is due to a certain bug that our team is currently working to resolve. The bug involves an unintended interaction between the column INVOICED_IMPRESSIONS and custom fields. Once that bug is resolved, then this thread will be considered resolved. However, your issue would still remain, since you are not using INVOICED_IMPRESSIONS in your report. It is helpful to us to keep unrelated problems on separate threads. Even though you are getting the same error, it is not necessarily for the same reason. Therefore, if you open a New Topic, someone will be able to address your specific problem.

Thanks,

Donovan McMurray, DFP API Team

[Donovan McMurray (DFP API Team)]

Hi, Gary.

Thanks for your patience while our engineers fixed this issue. The problem has been resolved, and I successfully ran the report in question on your account from both the UI and the API.

Please verify that everything is working on your end, and definitely reach back out if anything else comes up.

Thanks,

Donovan McMurray, DFP API Team