Lzzz666 commented on PR #50371: URL: https://github.com/apache/airflow/pull/50371#issuecomment-2999203027
> [eladkal](https://github.com/eladkal) [on May 22](https://github.com/apache/airflow/pull/50371#discussion_r2102327257) > Correct me if I am wrong but if import fails it means that the dag proccessor will never try to re-import it till the process is restarted. I think we need to change this. > I think this also explains why in some cases (in 2.x) after dag processor restart I see many dags as broken always with import errors on my own modules. About this problem: I'm not sure, but I tried to add an import of a non-existent module (causing a pre_import error), then removed that non-existent module. After waiting past the interval and letting the next scan run, the dag was retried and loaded successfully—no need to restart the dag processor. If this is right, it would mean that after we fix an import error in a dag file, it should be retried in the next cycle without having to restart the dag processor. But if this issue still occurs, should we open a new PR to address it? -- 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]
