rehan243 commented on issue #69658: URL: https://github.com/apache/airflow/issues/69658#issuecomment-4926945472
oh yeah, that "Task is in the 'None' state" error's bitten me before, especially after clearing with depends_on_past set. Honestly, the thing is, Airflow gets a bit confused on backfill runs when depends_on_past is true and previous runs are cleared or missing. The scheduler can't always figure out what the "previous" is supposed to be, so it won't transition to scheduled/running. I've had cases where I had to manually mark old runs as successful just to get things unstuck. Not gonna lie, the docs are super vague about this edge case, but it usually boils down to the metadata DB not reflecting a valid prior run state. Sometimes, restarting the scheduler or clearing just the specific task instance (instead of the whole DAG run) helps, but that's hit or miss. Are you seeing this only on 3.3.0? Curious if you tried toggling depends_on_past off temporarily to unblock it, or running airflow jobs manually (like airflow tasks run) to force progression? -- 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]
