'MWAA Airflow no_status for some specific tasks
Solution 1:[1]
There's no reason why your Tasks wouldn't execute in the order you've told them via bitshift, unless you have set the trigger rules away from all_success to all_failed for example. Especially if there's nothing in the logs, it implies that your encrypt_to_stage task has been set up to not execute if the previous tasks are successful.
A less likely possibility is that you've hit this known issue, but I'd expect your results to be more random than what you've shared (unless there are other DAGs that are running in parallel that complete at the same time as these first two tasks).
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | Thom Bedford |



