GitHub user PowerToThePeople111 edited a comment on the discussion: Some tasks 
in mapped tasks fail before starting, logs are empty

I experienced the same. Without sharing the exact code, I can say, that my dag 
is just a chain of sequential virtualenv tasks. The first one is mapped and 
exhibits the same problem as the issue-starter: some mapped tasks are in failed 
state although they have no start or end date.  Also they do not even try to be 
re-executed: although retries are possible, they failed finally already on 
their first try.

Another also strange thing I observed is, that initially there are 4 mapped 
tasks (1-4) queued. But instead of taking one of those initially mapped tasks 
as a second one to process, it will just take another one (the 5th) leaving the 
other ones waiting. Could it be, that this is causing the issue: like some kind 
of time out?

GitHub link: 
https://github.com/apache/airflow/discussions/42039#discussioncomment-11341165

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to