omkar-foss commented on issue #43171: URL: https://github.com/apache/airflow/issues/43171#issuecomment-2650000968
Yes, I'm looking into adding a new exception class `AirflowEnumeratedException` as described in the excerpt below from [this comment](https://github.com/apache/airflow/pull/44616#issuecomment-2639787911): >I think the next step could be to add a framework, where we could have a way to add the ERRORID to (say) AirflowException - or maybe beetter create AirflowEnumeratedException with obligatory error ID following the convention described here). Also the [markdown table](https://github.com/apache/airflow/blob/main/dev/AIRFLOW_ERROR_GUIDE.md) right now as it stands is intimidatingly huge. So just a random thought, I'm thinking may be we can eventually replace the markdown table with an Airflow CLI command - something like `airflow help <errorid>`. Let's say a user gets an exception showing ERRORID `AERR052`, example command as follows: ``` $ airflow help AERR052 The error you're facing would be with this message: "Failed to resolve template variable". As per our observations, a possible cause could be as follows: Triggered when a task's templated field contains errors or undefined variables. To resolve this, as first step, you can try the following: Review the task templated fields for any errors or undefined variables. Ensure all variables are defined and passed correctly in the DAG. If this doesn't resolve your problem, you can check out the docs for more info: https://airflow.apache.org/docs/apache-airflow/stable/concepts/operators.html#templating You may also ask your questions on the Airflow Slack #user-troubleshooting channel: https://apache-airflow.slack.com/messages/user-troubleshooting Happy Debugging! 🐞 ``` -- 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]
