You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per users' feedback in the Airflow Debugging Survey 2024, around 41.7% respondents don't consider error messages as actionable. Overall feedback also suggests that users find some error messages vague and confusing.
Use case/motivation
Goals for this issue are the following:
Identify and revise error messages that are vague, lack context, or do not provide clear guidance on resolving issues.
Provide detailed information, context, and actionable steps within the error messages to help users troubleshoot.
Transform error messages with meaningful linking wherever possible. e.g. an error like Celery command failed on host can be transformed or displayed with something like "Please check your DAG processor timeout variable for this". So the user has a starting point to start debugging.
omkar-foss
changed the title
Improve clarity, specificity, and actionable guidance in Airflow error messages
Make Airflow error messages more specific, clear and actionable
Oct 18, 2024
Description
As per users' feedback in the Airflow Debugging Survey 2024, around 41.7% respondents don't consider error messages as actionable. Overall feedback also suggests that users find some error messages vague and confusing.
Use case/motivation
Goals for this issue are the following:
Celery command failed on host
can be transformed or displayed with something like "Please check your DAG processor timeout variable for this". So the user has a starting point to start debugging.Related issues
Parent Issue: #40975
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: