- While no dedicated restart option exists, adding/removing/altering an arbitrary configuration override or log level option will force a restart.
Stopping an environment is not an option as there are numerous dependencies in Airflow such as the meta database that cannot be easily stopped. As an alternative, environments can be created and destroyed via API or CloudFormation.
- MWAA is running open source Airflow, either 1.10.12 or 2.0.2, and does not alter it's behavior. If the web server is not being updated to the lack of errors, it is likely that the scheduler responsible for serializing the DAGs has not completed or still sees errors. See your DAG processing logs in CloudWatch (may require INFO level logging). You can also debug locally using https://github.com/aws/aws-mwaa-local-runner
Can't run airflow backfill via cliasked 2 years ago
How to execute parallel dags in Airflow in EC2 Instanceasked 7 months ago
MWAA apache-airflow-providers-amazon DAGS can't import operatorasked 3 months ago
Cloudwatch alarms with Airflow MWAAasked 9 months ago
Airflow Web Server crashes when deployingasked 9 months ago
Broken DAG: No module name 'airflow.providers'asked 2 years ago
DAG import errors are not disappearing in the UI even after resolving themAccepted Answerasked a year ago
Error while trying to access web UI (MWAA)asked 8 months ago
Fetching logs in Airflow UI results in a timeout
Ability to temporarily stop Airflow planned?