Create notification UX for HITL and Deadline Alerts

[bbovenzi]

Description

Create an in-app notification UX across the Dashboard, Dag and Asset pages that allows a user to see important alerts like pending HITL actions and deadline alerts triggered. Plus any other future notifications that would be important to a user.

A user should be able to click on the notification for a modal that gives the user a quick summary and an action, but also include a link to the dag or task in question for full context.

There should also be a next action, like in emails to allow a users to quickly go through all active notifications without having to navigate tons of separate pages.

Use case/motivation

With HITL actions and deadline alerts, there is a lot more for a user to respond to than run and task failures.

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[parkhojeong]

It looks like there’s nothing in progress yet. I’d like to work on this

[bbovenzi]

@parkhojeong Go for it!

I'd suggest posting screenshots here before you have a polished PR ready. Figuring out the best UX is the important task here.

[parkhojeong]

@bbovenzi Thanks!

I’ll start working on it and post screenshots here first.

[parkhojeong]

@bbovenzi
Here's a demo I've been working on

Could you give me feedback?

Screen.Recording.2026-05-20.at.02.54.41.mp4

[bbovenzi]

Very cool! I don't know if we want a top-level nav for this, but we can surface this in a few places:

• dashboard page: on the button that says how many required actions there are
• dag page or dags list card: similar required actions button
• browse -> required actions: perhaps as a drawer instead of a modal since we will already have a table on the page

Also, let's focus on just HITL for now.

[parkhojeong]

Thanks for sharing thoughts! I focused on just hitl and addressed the dashboard page and browser -> required actions

• dashboard page: when the button is clicked, show a modal for all hitl.
• browse -> required actions: when a row is clicked, show a drawer for the task.

Screen.Recording.2026-05-26.at.23.20.11.mp4

Question

• dags list card: the exsiting "Required Actions" button is a filter. I think we have two options.
  • option1: Add a new "Required Actions" button near the "Required Actions" filter.
  • option2: when the "Required Actions" filter is clicked and row-level "Required Action" button is clicked, show the modal for that dag.
• dag page: I'm not sure whether we need to change this action

[bbovenzi]

Looking great!

dags list card - The filter is broken, since the dag card won't show the required actions badge without actually filtering the dags list for it. I think we need to fix the issue that we can't tell which dags will have HITL without expliciting filtering for it or waiting to get a 404 on fetching HITL details per dag. That is a separate PR. But I do like that clicking on the badge on the dag card would open the same modal.

dag page - Let's move the pending actions button into the header. We should remove the tab navigation in favor of this modal set up. But we will need backward compatibility of any old links by checking the URL route and opening the modal.

[parkhojeong]

Thanks for the reply

Addressed the requested changes

• dag list card: open the same modal when the badge on the dag card is clicked.
• dag page
  • move the pending actions button into the header
  • backward compatibility: open the modal for /required_actions

Screen.Recording.2026-05-28.at.19.15.54.mp4

Question

• dag page - the existing Required Actions tab includes both pending and completed hitl tasks, with filters. but new modal currently covers only pending hitl tasks, since we focused on the pending hitl. For backward compatibility, should the modal also support completed hitl tasks and filters ? i think word Required Actions fits pending tasks better, but the history may still be useful to some user.

[bbovenzi]

Looking great!

I think the modal can filter to just pending actions by default. But we can let a user see completed actions. The information already should show up in task logs and the task instance audit log too.