Marco, This is a good idea.
Though I am not sure if the name is right. While it helps some "business users" better understand DAGs, this is really more about adding automated DAG summaries—it does not really make it "business oriented on it's own". Whether it's business-user oriented or not is secondary; it could be included in the AIP's motivation, but the title suggests something much more complete and different than a "Dag summary". I can very easily imagine that this will be used also for technical summaries for non-business purposes. I was a bit put-off by seeing the title - because it sounded very "pompous" and something like - "let AI explain to business users what the Dags are doing" kind of feature (which is likely not something we want to do probably - yet)" - so I was thinking "well, not worth to look at it" - but when I actually looked at it I realized this is a straigthforward and rather simple thing to add (and pretty useful if you ask me). Dheeraj, > One suggestion here would be the ability to edit the summary directly from the web-ui if needed. I think the whole purpose of that one is to be generated dynamically during Dag execution. Since we already have Notes, that can be updated, I think that feature should be strictly "update by Dag only". We strongly want to avoid handling cases where the Dag overwrites a field that a user manually updated in the UI. Conflict resolution or priority rules sound pretty complicated for such a feature. J. On Thu, Apr 16, 2026 at 4:48 AM Dheeraj Turaga <[email protected]> wrote: > Huge +1 for this one. > > We have been relying on Notes in Airflow-2 to add short summaries about > dagruns and task instances which our Program Managers quickly glance at. > This is missing in Airflow-3. > We do have Notes, however it is additional clicks to get to the needed > information and it not very obvious which dagrun has notes. > > One suggestion here would be the ability to edit the summary directly from > the web-ui if needed. > > I think this is a good addition and if voted in, I would like to help with > its development aswell! > > Thanks, > Dheeraj > > On Wed, Apr 15, 2026 at 3:48 AM Kuettelwesch Marco (XC-AS/ESE6-ADA) via dev > <[email protected]> wrote: > > > Hello everyone, > > > > We would like to start a discussion on AIP-102: Improving Business User > > Interaction with Apache Airflow. > > > > In our Airflow deployment, many users need a quick understanding of task > > outcomes without reading full technical logs. In Airflow 2.x, we worked > > around this by auto-populating task and DAG notes with short > human-readable > > summaries. After moving to Airflow 3, that approach became less effective > > for UX and architecture reasons. > > > > AIP-102 proposes an optional Summary concept for DAG runs and task > > instances: > > > > - machine-generated, read-only summaries (separate from Notes), > > - Markdown-based rendering in the UI, > > - focus on fast, business-friendly status and error understanding, > > - support for per-execution summaries (not static docs), > > - opt-in behavior for DAG authors and operators. > > > > The goal is to improve usability for non-technical users while keeping > the > > feature generic and optional for all Airflow users. > > > > AIP-102 is available here: > > https://cwiki.apache.org/confluence/x/dZM8G > > > > What are your thoughts and ideas about this improvement? > > We look forward to your feedback. > > > > Marco > > >
