AutomationConditions not working as expected #23740
Unanswered
scottincrypto
asked this question in
Q&A
Replies: 1 comment
-
Hi @scottincrypto, apologies for the late response, looks like this slipped through the cracks. Are you still experiencing this issue on the latest version of dagster, and if so are you able to produce a reproduction of this? The behavior you show in the screenshot is definitely confusing, but a fair number of changes have been made since then which may have ended up resolving this. At the very least, I can confirm that a simple example with upstream static partitioned assets appears to function as expected (waiting for all upstream static partitions to be materialized, then launching the downstream). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Please help me to understand the AutomationCondition logic below.
I have a time window partitioned dbt asset set to AutomationCondition.any_downstream_conditions(). Its update should be triggered by a couple of downstream on_cron() assets, but it's not working as expected.
It has a handful of upstream assets, some which are static partitioned. One of these is highlighted in yellow in the policy evaluation below:
The highlighted asset has been newly updated since the cron tick, however the top level for that condition (highlighted) isn't resolving to true. It seems to me to satisfy the OR condition. Forcing re-materializations of the static assets (or recording materialization events) doesn't seem to trigger the condition either. This is preventing the "all parents updated since" condition from resolving and stopping the materialisation of the asset.
This isn't a problem for the upstream assets which aren't static partitioned - the logic makes sense to me for these and appears to be working OK.
Can you help me understand what is going on?
Beta Was this translation helpful? Give feedback.
All reactions