firebasegoogle-bigqueryexportgoogle-analytics-4

BigQuery suddenly cannot export Firebase custom events properly


Before March 2025, all exports were normal and had been maintained for a year. But after March, data export stopped on 3.16. I deleted all exported data in BigQuery, and the data was exported for a few days the next day, and then stopped exporting again on the third day. My other project does not have this problem and everything is normal.

Currently BigQuery uses sandbox.

I checked the BigQuery log, and the log showed the following error message:

WARNING 2025-04-19T07:14:23.431837840Z Source data not found for 'data$20250417'
  {
    "insertId": "erl6cee4fegy",
    "jsonPayload": {
      "message": "Source data not found for 'data$20250417'"
    },
    "resource": {
      "type": "bigquery_dts_config",
      "labels": {
        "config_id": "823826452107_4_22f8591f0f1d2d4185bc7f33aa955299",
        "project_id": "solitaire-fun-c23a7",
        "location": "us"
      }
    },
    "timestamp": "2025-04-19T07:14:23.431837840Z",
    "severity": "WARNING",
    "labels": {
      "run_id": "6878874f-0000-2540-8891-24058875dfd8"
    },
    "logName": "projects/solitaire-fun-c23a7/logs/bigquerydatatransfer.googleapis.com%2Ftransfer_config",
    "receiveTimestamp": "2025-04-19T07:14:24.527014233Z"
  }

I checked the location of the dataset, the use of quotas, and the setting of permissions, and there were no problems. But the export was still incorrect. Finally, I deleted the dataset in BigQuery, re-enabled and associated BigQuery in Firebase and GA4, and waited for a day. The dataset was recreated, but the data was still abnormal.

Please help me, how to solve this problem, thank you very much!


Solution

  • 1. Check BigQuery's Jobs Explorer for a detailed description of the problem.

    2. My problem was that the free storage capacity exceeded the limit, resulting in error code 7 for daily export jobs. Although the sandbox capacity I saw was 0GB/10GB, it was still determined that I exceeded the limit.

    3. The final solution was to upgrade the BigQuery sandbox to the Blaze solution.