Re: Performance problems downloading criteria report via API

2017-06-20 Thread 'Shwetha Vastrad (AdWords API Team)' via AdWords API Forum
Hi All, I'm marking this thread as duplicate of this one: https://groups.google.com/d/msg/adwords-api/MfX0XL7G4o4/c_40PK51AgAJ Please follow the other thread for updates about this issue. Regards, Shwetha, AdWords API Team. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find

Re: Performance problems downloading criteria report via API

2017-06-14 Thread 'Shwetha Vastrad (AdWords API Team)' via AdWords API Forum
Hi Tomas, We are aware of the issue and are investigating the latency in report downloads in AdWords API. The original issue has been fixed and you should no longer be seeing this error. I'll update this thread once I have more details. Regards, Shwetha, AdWords API Team. -- --

Re: Performance problems downloading criteria report via API

2017-06-14 Thread Tomas R
Also, we see a significant performance decline since few days ago using reporting API. On Wednesday, June 7, 2017 at 11:35:48 PM UTC+2, Shwetha Vastrad (AdWords API Team) wrote: > > Hi all, > > The team is working on a solution as a top priority. I'll keep you > notified once I have more

Re: Performance problems downloading criteria report via API

2017-06-07 Thread 'Shwetha Vastrad (AdWords API Team)' via AdWords API Forum
Hi all, The team is working on a solution as a top priority. I'll keep you notified once I have more updates. Regards, Shwetha, AdWords API Team. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/

Re: Performance problems downloading criteria report via API

2017-06-07 Thread raghu
I am upgrading to version 201705 and I get the below error. I go back to my older version of 201702 and I still see the same issue. googleads.errors.AdWordsReportBadRequestError: Type: ReportDownloadError.ERROR_WRITING_REPORT_TO_FILE Trigger: Unable to create report Field Path: None -Raghu On

Re: Performance problems downloading criteria report via API

2017-06-06 Thread 'Shwetha Vastrad (AdWords API Team)' via AdWords API Forum
Hi All, We are aware of the issue and we have implemented a fix. You should no longer be seeing this error. If you see it again, please get back to me. Regards, Shwetha, AdWords API Team. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+:

Re: Performance problems downloading criteria report via API

2017-06-06 Thread 'Shwetha Vastrad (AdWords API Team)' via AdWords API Forum
Hi All, Could you provide the clientCustomerIds along with the report definitions for the API requests which encountered this error? Please use *Reply privately to author* when responding. Regards, Shwetha, AdWords API Team. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also

Re: Performance problems downloading criteria report via API

2017-06-06 Thread Justin Coon
Hi we are experiencing errors similar to this with the CAMPAIGN_PERFORMANCE_REPORT. We either get an empty report(no errors) or we get an error ReportDownloadError.ERROR_GETTING_RESPONSE_FROM_BACKENDUnable to read report data Any thoughts API team? On Tuesday, June 6, 2017 at 9:26:03 AM

Re: Performance problems downloading criteria report via API

2017-06-06 Thread Dorian Kind
Hi all, just wanted to chime in to say that we've also been experiencing these errors more frequently again during the last few days. As opposed to the occurrence in April however, retrying almost always helps. Best regards, Dorian On Tuesday, 6 June 2017 15:58:28 UTC+2, Shwetha Vastrad

Re: Performance problems downloading criteria report via API

2017-06-06 Thread 'Shwetha Vastrad (AdWords API Team)' via AdWords API Forum
Hi, Could you provide the report definition used along with the clientCustomerId for which this error occurred? Does this error occur consistently? Please use *Reply privately to author* when sending the requested details. Thanks, Shwetha, AdWords API Team. -- --

Re: Performance problems downloading criteria report via API

2017-06-06 Thread AdwAPI-TR
Hello there, I'm starting to get this error today. Report download failed. Underlying errors are Type = 'ReportDownloadError.ERROR_WRITING_REPORT_TO_FILE', Trigger = 'Unable to create report' 3 Nisan 2017 Pazartesi 23:41:29 UTC+3 tarihinde Nadine Sundquist (AdWords API Team) yazdı: > >

Re: Performance problems downloading criteria report via API

2017-04-04 Thread 'Nadine Sundquist (AdWords API Team)' via AdWords API Forum
Hello Paul, The only reasons I can think of you getting a RATE_EXCEEDED would be if you were retrying on error quite rapidly due to this issue or if you have Basic access, and you exceeded your

Re: Performance problems downloading criteria report via API

2017-04-04 Thread Paul Newbury
Cheers guys! I'm getting RATE_EXCEEDED, just curious if there's a way I can see what time this is reset in my account? Or, maybe, is this a knock on effect from the earlier issue? Thanks again On Monday, April 3, 2017 at 9:41:29 PM UTC+1, Nadine Sundquist (AdWords API Team) wrote: > > Hello

Re: Performance problems downloading criteria report via API

2017-04-03 Thread 'Nadine Sundquist (AdWords API Team)' via AdWords API Forum
Hello Everyone! We've resolved the issue. The duration of this issue lasted from March 31st until today. You should no longer be seeing this error. If you see it again, please get back to me. We're currently working on putting measures in place to ensure that this particular issue does not pop

Re: Performance problems downloading criteria report via API

2017-04-03 Thread 'Nadine Sundquist (AdWords API Team)' via AdWords API Forum
Hi Josh, Please start a new thread on this one. That'll make it easier for us to track and for people to +1 your particular issue. Thanks, Nadine, AdWords API Team On Monday, April 3, 2017 at 3:41:11 PM UTC-4, Josh Gabel wrote: > > We've been noticing a different type of reportdownload issue.

Re: Performance problems downloading criteria report via API

2017-04-03 Thread Josh Gabel
We've been noticing a different type of reportdownload issue. When running the following AWQL report request to v201702 we're getting a blank report returned. No actual errors reported, just a report with empty data rows. I have confirmed that we had campaigns that meet the conditions with

Re: Performance problems downloading criteria report via API

2017-04-03 Thread 'Nadine Sundquist (AdWords API Team)' via AdWords API Forum
Hi Alex, This issue in our code base started on March 31st and continued into today. My team is currently in the cleanup phase of resolving this issue, so things should be getting better. I'll give the all clear when the error is completely resolved. Best, Nadine, AdWords API Team On Monday,

Re: Performance problems downloading criteria report via API

2017-04-03 Thread Alex
Hey Vishal, I've realised we're getting the same issues as others here, with the Keywords Performance Report too. Saw the error last Friday, and again over the weekend, and this morning. Has anyone got any information about the potential cause? On Friday, March 31, 2017 at 8:16:01 PM UTC+1,

Re: Performance problems downloading criteria report via API

2017-04-03 Thread 'Nadine Sundquist (AdWords API Team)' via AdWords API Forum
Greetings AdWordsians, This does appear to be an issue on our side. We're actively working on a solution. I'll get back to you when the problem is fully resolved. Best, Nadine, AdWords API Team On Monday, April 3, 2017 at 12:10:17 PM UTC-4, Addams wrote: > > I was now able to run our

Re: Performance problems downloading criteria report via API

2017-04-03 Thread Addams
I was now able to run our application that pulls data from the reports API successfully on 4/3/2017 at 11:56 AM EDT. Not sure if something was fixed, if the issue is just intermittent, or if I just got lucky. Hoping the issue is fixed. Thank you. On Monday, April 3, 2017 at 8:46:50 AM

Re: Performance problems downloading criteria report via API

2017-04-03 Thread Addams
We are also experiencing the same error when attempting to download the KEYWORDS_PERFORMANCE_REPORT data for 4/1/2017 as well using the reports API. We experienced this issue on 4/2/2017 at 9:03 PM EDT and again this morning, 4/3/2017 at 7:39 AM EDT. We are currently unable to pull our

Re: Performance problems downloading criteria report via API

2017-04-03 Thread Dorian Kind
Hi there, FWIW, we're also seeing lots of these errors since Saturday. Cheers, Dorian On Monday, April 3, 2017 at 6:38:09 AM UTC+2, cv wrote: > > Hello vishal, > > we are also facing same error since 31 march. We have also sent soap xml > to you. > > On Saturday, 1 April 2017 00:46:01

Re: Performance problems downloading criteria report via API

2017-04-02 Thread cv
Hello vishal, we are also facing same error since 31 march. We have also sent soap xml to you. On Saturday, 1 April 2017 00:46:01 UTC+5:30, LE Max wrote: > > We have been experiencing problems for the last several hours in > retrieving reports via the API. > > > > When we request a criteria

Re: Performance problems downloading criteria report via API

2017-04-02 Thread Vitaliy Shibaev
We also observe the same issue since 31 March - never seen that before: *Google.Api.Ads.AdWords.Util.Reports.AdWordsReportsException: AdWordsReportsException: One or more AdWords Report download errors have occurred.* *ReportDownloadError.ERROR_WRITING_REPORT_TO_FILE. (Error:

Re: Performance problems downloading criteria report via API

2017-03-31 Thread 'Vishal Vinayak (Adwords API Team)' via AdWords API Forum
Hi, Could you please provide me with the SOAP XML report definition, complete error logs and your 10 digit AdWords account ID? Please click on *Reply privately to author *when responding. Regards, Vishal, AdWords API Team -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us

Performance problems downloading criteria report via API

2017-03-31 Thread LE Max
We have been experiencing problems for the last several hours in retrieving reports via the API. When we request a criteria report, we are getting the following message: 'Unable to create report, Type: ReportDownloadError.ERROR_WRITING_REPORT_TO_FILE' We have made repeated attempts