Dev-iL commented on issue #43180:
URL: https://github.com/apache/airflow/issues/43180#issuecomment-3431431945

   One thing I came across recently:
   
   When we have code such as below in an operator, and unless one adds an 
explicit logging call, the task ends up being skipped silently with no 
indication of the reason (not even a "`AirflowSkipException` encountered - 
skipping"). I would expect a textual rendering of the "upstream" (custom) 
exception at the very least.
   
   ```python
   raise AirflowSkipException from CustomExceptionWithParameter(param1)
   ```


-- 
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]

Reply via email to