Re: custom time range not saved in ReportDefinition

Hi, I'll look into it, atm we've built an automatic retry system as a workaround to the issue. I'll try to get the latest failure data as soon as possible. It might take a short while. Cheers, Rohit -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion gr

Re: custom time range not saved in ReportDefinition

Hi Rohit, The core engineering team is having trouble replicating the behavior. Are you still seeing this issue and if so can send a request ID for a more recent example of it happening? Best, - Eric -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion

Re: custom time range not saved in ReportDefinition

Hi Rohit, Thank you for the information, I've forwarded it on to the core engineering team. Best, - Eric On Feb 22, 5:01 am, Rohit Dantas wrote: > Hi, > > The problem persists today. > > Request IDs that did not work: > >    - 3649d0052b00bc0bec61e789f0e0f5cf >    - 832441e21fd0d8b11d674a201726

Re: custom time range not saved in ReportDefinition

Hi, The problem persists today. Request IDs that did not work: - 3649d0052b00bc0bec61e789f0e0f5cf - 832441e21fd0d8b11d674a2017264583 - bc50230be7212c4f45efd2db254a9aee - c33c811451740b61a5f3c41dfd43b871 Request IDs that worked: - 2741005e8ff23ed765d91d0f4344 - a4678d0e

Re: custom time range not saved in ReportDefinition

Hi Eric, Sorry about the confusion, I misread the 'request ID' as 'report ID' for some reason. The report failed again and in the soap_xml.log the request ID saved was *652b5a957c66dd412fa722032004ffbf* Hope that helps with identifying the error. Cheers, Rohit -- =~=~=~=~=~=~=~=~=~=~=~=~=~=

Re: custom time range not saved in ReportDefinition

Hi Rohit, Can you send me the request IDs (from the response header) of a request that doesn't work and one that does for the same report definition? That would help me in isolating the issue. Best, - Eric On Feb 15, 3:33 am, Rohit Dantas wrote: > Hi, > > the two reportIDs we use for which thi

Re: custom time range not saved in ReportDefinition

Hi, the two reportIDs we use for which this error occurs are: 1. 11931386 2. 11940986 As mentioned previously, the date update on the second report failed repeatedly yesterday. On the other hand it seems to work fine today. Cheers, Rohit -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Re: custom time range not saved in ReportDefinition

Hi Rohit, I don't have any further insight yet as to why this is happening. Could you provide me with the request IDs of a request that fails to update and then another of it later succeeding? Best, - Eric On Feb 14, 9:28 am, Rohit Dantas wrote: > Hi Eric, > > Sorry for the late reply, but I on

Re: custom time range not saved in ReportDefinition

Hi Eric, Sorry for the late reply, but I only just noticed your reply to the above issue as I was on holiday when Johannes wrote the above bug report. We have been subject to the same problem multiple times over the past 2 weeks, but quite sporadically. It will work without a hitch for a few da

Re: custom time range not saved in ReportDefinition

Hi Johannes, I'm not able to replicate this behavior in my own account, but the logs for this request do show that the date failed to change. Is this happening consistently or sporadically? Is it happening for only this one report definition or only this one account? Best, - Eric Koleda, AdWord

custom time range not saved in ReportDefinition

Hi! Since last Saturday 29th of January, we are experiencing trouble with setting the custom time ranges in our Reports. The problem is easily reproducable on our side using the Java Client Library: We assemble a new ReportDefinition and an according ReportDefinitionOperation (SET) to set the