AMP waiting on already updated parent about dagster HOT 5 CLOSED

Hi @OwenKephart, could you please clarify how the fix takes effect? I'm on Dagster Cloud Serverless and even after running my DBT DAG manually earlier in the day (to refresh the 'state' of all the assets), the assets downstream of my external assets are still not triggering at their AMP cron tick. The Automation page continues to say they're waiting for their (external asset) parents, which have already been updated.

Is the fix applied automatically for Cloud users or do I need to upgrade to the 1.6.9 release? I am on version 1.5.14 for your reference.

from dagster.

Just noticed this myself. Looks like the last time it worked was around 5 PM ET on 2/28.

from dagster.

Hi @mjkanji thanks for the report. We've identified the issue here and a fix has been rolled out to Dagster Cloud.

For OSS users, the same fix will be available in next week's 1.6.9 release, or reverting to 1.6.6 will also avoid this issue.

from dagster.

Hi @mjkanji apologies for the confusion here -- there was a secondary fix that needed to happen on the cloud end to fully solve this issue, which has now been rolled out (as of this morning). No action is required on your end if you are a cloud user.

from dagster.

Hi @mjkanji apologies for the confusion here -- there was a secondary fix that needed to happen on the cloud end to fully solve this issue, which has now been rolled out (as of this morning). No action is required on your end if you are a cloud user.

Awesome, thanks! I was also able to confirm that my DAGs are running as expected.

from dagster.