Issue with Google Ads Data Transfer in BigQuery - Error Code 3: No Jobs to Start

Google Cloud Compute Infrastructure
,
1

Hello,

I am experiencing an issue with a Google Ads Data Transfer setup in BigQuery. The transfer consistently fails with the following error message:

Error code 3: No jobs to start for run: projects/215452016218/locations/us/transferConfigs/66aa89b4-0000-2cee-8277-582429a84b54/runs/6770861c-0000-2b46-8b59-14223bcada62

Here are some important details about the situation:

Service Account Permissions:

The service account being used for the data transfer has the following permissions:

  • BigQuery Admin
  • BigQuery Data Editor
  • BigQuery Data Transfer Service Agent
  • BigQuery Job User
  • Cloud Build Service Account
  • Cloud Build Service Agent
  • Cloud Functions Service Agent
  • Cloud Pub/Sub Service Agent
  • Cloud Run Service Agent
  • Compute Engine Service Agent
  • Container Registry Service Agent
  • Dataform Service Agent
  • Logs Writer
  • Service Account Admin
  • Service Account Key Admin
  • Service Account Token Creator
  • Service Account User
  • Storage Object Admin

Attempts Across Different Projects: We have attempted running the data transfer from multiple projects within our organization, but the same error persists.

Incident Context: A few days before the issue started, there was an access granted to the service account via Cloud Shell. This access, for some reason, removed all existing permissions associated with the service account. We have since restored the permissions manually, but the problem persists.

Data Availability in Google Ads: I confirm that there is indeed data available in the Google Ads account for transfer.

Any insights or suggestions from the community on how to troubleshoot this issue would be greatly appreciated.

Thank you!

2

Hi @JCapurro,

Welcome to Google Cloud Community!

The “No jobs to start to run” error with your Google Ads BigQuery Data Transfer likely stems from using only match tables in your configuration. Match tables process once daily, transfer runs for previous dates may fail with this error.

Here are the possible solutions to fix your problem:

  • Set Refresh Window to 1: This limit runs to once per day.
  • Include Non-Match Tables: Add other tables to your transfer configuration’s filter.

Also, double-check the Google Ads account link in BigQuery. While you restored permissions after the Cloud Shell incident, verifying ensures everything’s correctly configured within the Data Transfer Service.

If the error persists, you might consider filing an issue request, as it could provide more specific guidance from our Engineering Team for your situation. Before filing, please take note on what to expect when opening an issue.

I hope the above information is helpful.

1 Like