Offline User Data Job Stuck in 'RUNNING' State

[Harris]

I'm trying to run remove operations using offline user data jobs to remove user identifiers from CRM based user lists. When I run the offline data jobs with email or phone number (contact information) user identifiers, the jobs resolve pretty quickly (never longer than an hour).

However, when the user identifier is an advertising ID, the jobs seem to get stuck - reporting that they are 'RUNNING' for a much longer amount of time, and I have yet to see one ever resolve. The example I'm looking at now has been running for over a week, for example.

Is this expected behavior? If so, is there a 'typical' amount of time this takes? Or is something wrong here?

Thank you!

[Harris]

Replying to my own message here for visibility, as it's been a little while. I'm still having this problem, and the jobs are still running as of a few minutes ago.

Some help here would be greatly appreciated,

Thank you!

[Google Ads API and AdWords API Forum]

Reposting the last inquiry (https://groups.google.com/g/adwords-api/c/DbfL_gh8swc/m/a5BPON3PBgAJ) from the forum as it wasn't routed to our support queue.

Cheers,
Ernie John
Google Ads API Team      

[jack heart]

Have you solved this problem now? I also encountered the same problem

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to Google Ads API Forum.

I understand that you have been encountering the same problem when running an offline user data job. With this, could you provide us with the complete API logs (request and response with request-id and request header) generated on your end? This is so our team could further check and provide more appropriate guidance.

If you haven't enabled the logging yet, logging can be enabled by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation, which you can access from this link (https://developers.google.com/google-ads/api/docs/client-libs?hl=en). For REST interface requests, you can enable logging via the curl command by using the -i flag.

You may then send the requested information privately via the Reply to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com  alias instead. 

Reference Links:

• request - https://developers.google.com/google-ads/api/docs/concepts/field-service#request
• response - https://developers.google.com/google-ads/api/docs/concepts/field-service#response
• request ID - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id
• request header - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers 

This message is in relation to case "ref:_00D1U1174p._5004Q2o9gMO:ref"

Thanks,
 

Google Ads API Team