Hi Vikram, Thanks for the email!
This looks packed already, but just in case if we have extra time, could we add a ~5-10 minute opening discussion on AIP-97 Task Failure Classification? I don’t see any other Discussion Topics listed on the agenda this time: A few of the maintainers shared earlier feedbacks - thank you!!, and we’ve been working closely with Amogh recently on addressing those, and reopened the dev-list discussion, separating failure classification from retry policy so AIP-97 can move forward independently. https://lists.apache.org/thread.html/3jof9hps77r957o8rlz5r54nm3glt1p2 Would love to briefly explain the problem and the proposed boundary, then get feedback on: • What evidence executors should provide to establish an infrastructure failure. • Whether the bounded infra retry approach preserves user-defined retry allowances with suitable safeguards. The goal for hopping on the call would be to identify open concerns and suitable reviewers, if the time is short for this dev call, would it be possible to propose this item on the agenda for next one? Thanks a lot! AIP-97: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=399279312 AIP-122: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974654 Best, Stefan ——— AIP-97 Task Failure Classification https://cwiki.apache.org/confluence/x/0ITMFw Airflow’s executor runs separately from the task worker, so it can still read backend failure details after the worker stops. AIP-97 passes confirmed causes, such as Kubernetes preemption, into failure handling for listeners, logs and metrics. When the cause is unclear, it stays unclassified. This helps integrations distinguish infrastructure interruptions from application errors and route alerts appropriately. Ordinary retries, clears and DAG callback interfaces stay unchanged. We’ve separated infrastructure retry decisions into: AIP-122 Infrastructure Retries https://cwiki.apache.org/confluence/x/-pXwGg When enabled, AIP-122 uses confirmed infrastructure failures to preserve ordinary task retries, within an administrator-configured limit. For example, consider a Spark task with retries=1. Its first attempt is interrupted by a confirmed Kubernetes preemption. The retry starts, but the Spark job fails during that second attempt. There is now no retry left: the user-defined retry was consumed by an infrastructure interruption rather than an application failure. With AIP-122 enabled, the first infrastructure failure can receive an infrastructure retry, leaving the ordinary retry available for the later Spark failure. > On Oct 7, 2026, at 5:04 PM, Vikram Koka via dev <[email protected]> > wrote: > > Hi everyone, > > Here is a quick reminder that we have our Airflow dev call tomorrow, > Thursday, 8th October 2026 at 8AM PT (11 am ET | 4 pm UTC / GMT). > > Proposed agenda: > > > > - Follow-up action items: > - > - Amogh to ask David to split the AIP-104 PR into stacked PRs so > batching can land independently of dynamic iteration. > - Rahul to check in with Bugra on AIP-94 and remove it from the > milestone if it's still inactive. > - Kaxil to reach out to the AWS and Google teams on Managed Agent and > ADK integration alignment. > - Shahar to test the "Runs On" self-hosted runner setup over the next > few days and progress AIP-118. > - Pierre and Jason to close out open TypeScript DAG scope and UX > questions before the next call. > - Community to help test the current large providers release, > especially Common AI, Google, Amazon, and Fab. > - > - Release updates - 3.4.0 (Rahul Vats) > - Development Updates > - AIP-111 Task Loops (Ash Berlin-Taylor) > - AIP-104 Task Iteration (David Blain) > - AIP-85 Dag Importer (Dilnaz Amanzholova) > - And, YAML Dags (TP Chung / Ephraim)? > - And, Typescript Dags (Jason Liu) > - Common AI 1.0 (Kaxil) > - Discussion topics: > - > - TBD > > > For additions to the agenda, please message me on Slack or send me an > email. I haven't had a chance to create a wiki page for this yet. The > summary of the call will also be sent to the mailing list and posted on the > same wiki page. > > As a reminder the zoom link is > https://astronomer.zoom.us/j/84124767391?pwd=3vatlR8OuF6Uy2JbOcKrw6034CayFG.1 > > Looking forward to seeing you all soon, > Vikram > > -- > > Vikram Koka > Chief Strategy Officer > Email: [email protected] > > > <https://www.astronomer.io/>
