Reconnect Cloud Batch jobs on task retry

[1fanwang]

A synchronous Cloud Batch task uses a caller-stable job ID. If its worker exits after submission, retry resubmits the same ID and fails with 409 ... already exists, even if the first job is active or succeeded.

On Airflow 3.3+, the operator saves the canonical name before waiting. Retry fetches only that task-owned job: wait if active, restore success, resubmit after NotFound, or reject other terminal states. Fresh and deferrable execution, durable=False, and older Airflow behavior do not change.

Testing

The regression test drives the real task state accessor and execute() with a local hook stand-in.

Raw retry proof

$ AIRFLOW_HOME=.build/cloud-batch-proof-home uv run --project providers/google pytest providers/google/tests/unit/google/cloud/operators/test_cloud_batch.py::TestCloudBatchSubmitJobOperator::test_retry_reconnects_to_running_job -xvs

# upstream/main
E   google.api_core.exceptions.AlreadyExists: 409 Job projects/testproject/locations/us-central1/jobs/test already exists
=================== 1 failed, 1 warning in 113.59s (0:01:53) ===================

# this branch
PASSED
=================== 1 passed, 1 warning in 92.69s (0:01:32) ====================

---

Was generative AI tooling used to co-author this PR?

• Yes (GitHub Copilot CLI, GPT-5.6 Sol)

Generated-by: GitHub Copilot CLI (GPT-5.6 Sol) following the guidelines

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[potiuk]

Hello @1fanwang - thank you for your contributions to Apache Airflow!

The Airflow community has introduced a limit of 5 open pull requests at a time for contributors without write access to the repository. You currently have 34 open pull requests, so - as a one-time step of introducing the limit - we closed the ones where maintainers have not engaged yet:

• Report failure causes and bound infrastructure replacements #66405 - Report failure causes and bound infrastructure replacements
• Honor AirflowFailException raised inside on_retry_callback #66781 - Honor AirflowFailException raised inside on_retry_callback
• Emit OpenTelemetry spans from airflow CLI entry points #66789 - Emit OpenTelemetry spans from airflow CLI entry points
• Preserve sensor start_date when scheduler advances reschedule to queued #66790 - Preserve sensor start_date when scheduler advances reschedule to queued
• Reuse the resumable core for TriggerDagRunOperator's durable wait #68955 - Reuse the resumable core for TriggerDagRunOperator's durable wait
• Let TriggerDagRunOperator own its execution via a new accessor #69135 - Let TriggerDagRunOperator own its execution via a new accessor
• Add resumable_job.reconnect_failure metric for failed reconnects #70653 - Add resumable_job.reconnect_failure metric for failed reconnects
• Allow configuring the collation of asset name columns #71249 - Allow configuring the collation of asset name columns
• Fix task_instance_history downgrade failing under the PyMySQL driver #71258 - Fix task_instance_history downgrade failing under the PyMySQL driver
• Correct the retry_db_transaction docstring about provide_session #71311 - Correct the retry_db_transaction docstring about provide_session
• Show worker pod logs for tasks that failed before writing any log #71566 - Show worker pod logs for tasks that failed before writing any log
• Reconnect Synapse Spark batches on task retry #72368 - Reconnect Synapse Spark batches on task retry
• Reconnect Azure Data Factory pipelines on task retry #72399 - Reconnect Azure Data Factory pipelines on task retry
• Prevent duplicate Anthropic batches on task retry #72400 - Prevent duplicate Anthropic batches on task retry
• Reconnect AWS Batch jobs after worker crashes #72413 - Reconnect AWS Batch jobs after worker crashes
• Reconnect Airbyte sync jobs after task retries #72414 - Reconnect Airbyte sync jobs after task retries
• Reconnect Data Fusion pipelines after task retries #72415 - Reconnect Data Fusion pipelines after task retries
• Prevent duplicate OpenAI batches on task retry #72416 - Prevent duplicate OpenAI batches on task retry
• Recover Dataproc jobs after worker crashes #72417 - Recover Dataproc jobs after worker crashes
• Recover Athena queries after worker crashes #72419 - Recover Athena queries after worker crashes
• Reconnect Cloud Batch jobs on task retry #72420 - Reconnect Cloud Batch jobs on task retry
• Prevent duplicate ECS submissions on task retry #72421 - Prevent duplicate ECS submissions on task retry
• Recover Databricks SQL statements after task retries #72422 - Recover Databricks SQL statements after task retries
• Reconnect dbt Cloud runs after worker crashes #72423 - Reconnect dbt Cloud runs after worker crashes
• Restore missing serialized Dags without a full reparse #72927 - Restore missing serialized Dags without a full reparse
• Report task failure causes without changing retries #73350 - Report task failure causes without changing retries

These pull requests stay open because maintainers are already engaged in them - they count towards your limit:

• Add durable option to TriggerDagRunOperator to reconnect on retry #68936 - Add durable option to TriggerDagRunOperator to reconnect on retry
• Let deferrable tasks reconnect without polling #68952 - Let deferrable tasks reconnect without polling
• Retry transient database errors in the metastore secrets backend #71307 - Retry transient database errors in the metastore secrets backend
• Return each attempt's own URL from operator extra links #71522 - Return each attempt's own URL from operator extra links
• Return 404 instead of 500 when DagRun is missing in Execution API #72907 - Return 404 instead of 500 when DagRun is missing in Execution API
• Edge: Return 404 for missing task logs and emit failed job metrics #72908 - Edge: Return 404 for missing task logs and emit failed job metrics
• Edge: Return 400 instead of 500 on invalid worker version #72925 - Edge: Return 400 instead of 500 on invalid worker version
• Return 404 for task-state writes after a Dag run is deleted #72926 - Return 404 for task-state writes after a Dag run is deleted

This is not a judgement of you or of your changes. We never told contributors before that opening many pull requests at once was a problem, so there is nothing to feel bad about - and nothing is lost: your branches, commits and the review history stay where they are.

What we ask you to do is to make your first prioritization decision: choose which of the pull requests above matter most to you, and reopen them (up to 5 open at a time, including the ones still open) with the "Reopen pull request" button or gh pr reopen <PR_NUMBER> --repo apache/airflow. Reopen the ones you are ready to follow through - keep them rebased, respond to review comments and fix failing checks.

While your pull requests are waiting for review, the most valuable thing you can do is help in other ways - reviewing other contributors' pull requests, helping with issues, and taking part in the discussions on the devlist and Slack.

Why we introduced the limit, what it means for you and how to reopen or restore a pull request is explained in https://github.com/apache/airflow/blob/main/contributing-docs/32_open_pull_request_limit.rst.

---

Drafted-by: Claude Code (Opus 5); reviewed by @potiuk before posting