Hi,
The PENDING status means the job has not started. This could happen
for two reasons:
1) The job hasn't received all of the defined parts yet (the parts
received is less than the numRequestParts field).
2) There are jobs ahead of it in the queue that are PROCESSING or
PENDING (only one job ca
Okay .. that helps !
Have one more question though .. I am trying to test failures in the
sandbox environment by putting through mutate jobs I know will fail
using the bulk service. My jobs stay 'Pending' though, and never seem
to get processed. Is that normal behavior? Does a job that causes a
Hi Sidd,
The index in the failure result doesn't point to an operation stream,
it points to the operation within a stream. To determine which
operation stream to look in you need to count which operation stream
result you are in, and then look in the corresponding operation
stream. So if you are
Hi ..
Thanks for your answer. Unfortunately, it's still unclear to me how
to extract the actual entity that failed. If I have the index into
the operation stream, how do I know which operation within that stream
failed?
On Feb 9, 7:51 am, AdWords API Advisor
wrote:
> Hi Sidd,
>
> The Failure
Hi Sidd,
The FailureResult exists within an OperationStreamResult. There is a
one-to-one correlation between OperationStreams and
OperationStreamResults. The index in the field path of the error in
the FailureResult is relative to the OperationStream that correlates
to the current OperationStrea
