v201601 Batch job service error 403

[Clément Picou]

Hello,

since I've migrated to v201601 I've got a 403 error when I upload entities with the batch job service.

The job add operation works but the upload doesn't. The message is "Failed to upload operations for batch job."

Thank you 

Clément

[Yin Niu]

Hi Clément，

Are you able to access the upload URL? What type of operations do you have in your batch job? 

Thanks,

Yin, AdWords API Team. 

[Jbielsa]

In v201601, you need to make an additional call to exchange the bulk upload URL for a resumable upload URL. The relevant change in code is this line: https://github.com/googleads/googleads-dotnet-lib/blob/master/examples/AdWords/CSharp/v201601/CampaignManagement/AddCompleteCampaignsUsingBatchJob.cs#L163

[Clément Picou]

Thank you. My bad, I didn't read the migration guide :-(

Now I've got another problem : when I try to get the completed job, the status is always "AWAITING_FILE" for a loooooong time (and I'm just uploading 30 campaigns), as if I didn't start the upload.

Here's my code (I'm using the .NET client library)  : 

int delay = MUTATE_JOB_DELAY;

            BatchJobUtilities batchJobUploadHelper = new BatchJobUtilities(_user);

            BatchJob batchJob = null;

            try

            {

                BatchJobOperation operation = new BatchJobOperation { @operator = Operator.ADD, operand = new BatchJob() };

                var res = _batchJobService.mutate(new BatchJobOperation[] { operation });

                if (res != null && res.value.Count() > 0)

                {

                    batchJob = res.value.FirstOrDefault();

                }

                else

                {

                    logger.Error("Unable to create job in account {CustomerId}", _customerId);

                    return -1;

                }

            }

            catch

            {

                return -1;

            }

            if (batchJob != null)

            {

                string uploadUrl = batchJob.uploadUrl.url;

                string resumableUploadUrl = batchJobUploadHelper.GetResumableUploadUrl(uploadUrl);

                for (int i = 0; i < NB_MUTATE_JOB_RETRIES; i++)

                {

                    try

                    {

                        batchJobUploadHelper.Upload(resumableUploadUrl, operations);

                        return batchJob.id;

                    }

                    catch(Exception e)

                    {

                        Thread.Sleep(delay);

                        delay = (int)(delay * 1.33);

                    }

                }

                logger.Error("Unable to upload operations in account {CustomerId} after "+NB_MUTATE_JOB_RETRIES+" retries", _customerId);

                return -1;

            }

            else

            {

                logger.Error("Unable to create job in account {CustomerId}", _customerId);

                return -1;

            }

Thank you

[Jbielsa]

Hi. 

On Feb 16. There is a question with title "BatchJobService not completing" about the AWAITING FILE STATUS and Google respond with "The engineering team is working on this issue. We will update you once the issue is fixed."

[Yin Niu]

Hello, 

This has been fixed. Please try again. 

[Clément Picou]

It still doesn't work, but the problem has evolved :-)

The job status is DONE but the problem is when I download the results : 

- I've got the same number of mutate results than of operations. That's ok

- Foreach mutateresult, errorlist is not null but errorlist.errors is null

- Foreach mutateresult, mutateresult.result is null

- No entity has been published

Thank you

Clément

[Yin Niu]

Hi Clément, 

Could you please send the SOAP request and response logs? Please click Reply privately to author in the forum when responding. 

[Thanet Knack Praneenararat (AdWords API Team)]

Hi Clement,

The issue you've reported should be fixed now.

Please let us know if you still see those issues.

Best,

Thanet, AdWords API Team