Re: [I] Add a new task instance status: ICED [airflow]

["eladkal (via GitHub)" <gi...@apache.org>]

eladkal commented on issue #42459:
URL: https://github.com/apache/airflow/issues/42459#issuecomment-2618144350

   > Let's say we have a DAG with three tasks: A >> B >> C.
   During the day2day work, there might be some occurred in task B which is caused by external, ie the error is not caused by a bug of the code. In such cases, we want to "skip" this task, so during the schedule the new flow looks like this: A >> C.
   Please note the "skip" here is different with the Airflow built-in skip, this is something we'd like to call it ICED. If a task is ICED, all the downstream tasks will continue to run even they set the trigger rules to 'all success'.
   
   The easy and best solution to my taste is to manually mark B as success and leave a note on the task of what you fixed. The note will make the task square be half colored makes it easy to track
   
   <img width="101" alt="Image" src="https://github.com/user-attachments/assets/91988110-2f0e-41e6-bfc6-99cb03bcc894" />
   
   I'm closing this issue as your use case is solved natively without the need to introduce new task state.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org