cmarteepants opened a new issue, #53683: URL: https://github.com/apache/airflow/issues/53683
### Description Follow up to PR #53035 (initial HITL UI) UI currently collects a user's response but does not persist it, surface it on reopen, or record it in logs. This limits audibility and user feedback. **Problem Statement** - Approving users can't see what they (or someone else) selected after the fact - Airflow Admins and Users do not have no immutable record of who responded, when, and with which option - Debugging HITL-related failures is harder because the chosen value is absent from task logs ### Use case/motivation 1. Persist response: - Store things like `user_id`, `option_value`, `option_label` and `responded_at` in the database when a HITL trigger is resolved - API: Extend API to return the saved payload 2. Surface response in UI payloads: Endpoints should include the stored response under a key like `hitl_response` 3. Log for audibility: - After successful save, write a structure line to task logs like `[HITL] user=alice option="Approve" at 2025-07-23T14:02:11Z` - Emit the same data to the Airflow audit log if enabled 4. UI fallback - If `hitl_response` exists, display a read-only banner: `Responded “Approve” by Alice at 14:02` - Disable further edits unless the operator explicitly allows overrides. ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
