SameerMesiah97 opened a new pull request, #67382: URL: https://github.com/apache/airflow/pull/67382
**Description** This change fixes an issue (as reported in Issue #64048) affecting `AirbyteTriggerSyncOperator` in deferrable mode that was not fully resolved by PR #64051. Previously, `execution_timeout` was passed directly to `defer()`. The operator now explicitly passes `timeout=None` to `defer()` while still preserving `execution_deadline` handling within the trigger/operator flow. **Rationale** In deferrable mode, Airbyte job cancellation is performed within `execute_complete()` when the trigger emits a timeout event. However, framework-level deferred timeout handling bypasses `execute_complete()` entirely and does not invoke `on_kill()` in the triggerer process. As a result, Airbyte jobs could continue running after the Airflow task timed out, leading to leaked workloads and excessive resource consumption. While this weakens the framework-level deferred timeout guarantee, in this case preventing leaked external workloads takes precedence because there is currently no equivalent cleanup path in the triggerer process. This change keeps timeout handling within the trigger/operator flow so Airbyte job cancellation can occur correctly. **Tests** Added an operator-level regression test verifying that `defer()` is called with `timeout=None` while `execution_deadline` handling remains preserved for Airbyte job timeout cancellation processing. **Backwards Compatibility** This change does not modify public APIs or method signatures. Related: #64048 ##### Was generative AI tooling used to co-author this PR? - [X] Yes (please specify the tool below) Generated-by: [GPT 5.5] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
