potiuk commented on issue #41101: URL: https://github.com/apache/airflow/issues/41101#issuecomment-2257410949
I think you should realise that we have absolutely no idea about your setup and screenshots are not helping to understand that, so people here can't even know what is wrong. People here will simply miss context. The only way it can be acted upon is if there are correlated logs - i.e. find a concrete DAGs that has been triggered wrongly. You can set debug log level on the whole airflow (but I have no idea how to do in MWAA - likely there should be docs) https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#logging-level and you can get scheduler logs (again no idea how to do it in MWAA) - correlated with the DAG that gets triggered wrongly - showing why it has been scheduled and explaining the context. Explaining what has been triggered, why you think it should not be and showing related log entries. You have to remember - that here people here when they think they can help - in their free time - and it's up to you to provide detailed information (that they don't have), so such a vague issue does not help those people (who often do it at expense of their free time) does not help them - simply this is not a helpdesk but a forum where people help each other if they can. But also remember that MWAA is a service you pay for and that they can likely access all the information that people here can't - so if you won't be able to extract and provide the information with more details, then you pay for the service and I guess they should be able to investigate more - with all the access and possibilities to look at your problem. -- 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]
