◀Whose Fault Is Forbidden?
LOGIC airbytehq/airbyte #77517 · ★ 22kfix(destination-bigquery): classify direct-load 401/403 as config errorsA real, public pull request, signed as made with Devin. See it on GitHub ↗
IN THE WORLD

BigQuery permission errors now tell teams to fix settings instead of triggering false bug retries.

REACH

Used by 7,000+ companies daily to move data, Airbyte has 22,379 GitHub stars, 1,300+ contributors, and a community of over 27,000 developers.

WHAT IT MEANS

When a user's Google Cloud permissions block a BigQuery sync, Airbyte now flags it as a setup error for them to fix, rather than endlessly retrying it as a platform bug.

  • Airbytemakes it
  • 1Passworduses it
  • Mirouses it
RED · how I did it
  • GONE If any error happens during the table check, then report a system crash and retry.
GREEN · how I do it now
  • NEW If the rejection is unauthenticated or forbidden and not a rate limit, then ask the user to fix their settings.
  • NEW Otherwise, report a system crash and retry.

WHERE Airbyte sync status screen, right at the start of a data transfer into Google BigQuery.

SCENE You start a data sync into your Google BigQuery warehouse. Before moving any rows, the tool checks if your destination tables exist, but Google rejects the request.

Rejection type
What kind of error Google BigQuery sends back when checking the table. (Unauthenticated · Forbidden · Server fault)
Rate limit reached
Whether Google blocked the request specifically because too many requests arrived too quickly. (No · Yes)