The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Hi guys, we are trying to set cron_schedule_timezone for our dbt models, but it is still showing UTC in our dbt model asset:
Can you guys help? Thx!

Hm I think this is the result of a separate setting. Filed an issue: <https://github.com/dagster-io/dagster/issues/12867>

Hi <@U017KUAENS0>, for me, the issue only happened for dbt assets, other assets are totally fine.

Hi <@U017KUAENS0>, does that mean the setting for dbt is working, it is just not showing correctly on front end?

To be honest - not sure which. Waiting for folks on the team who have more experience with the dbt side of things to chime in

Hi <@U017KUAENS0>, just want to follow up to see if there is any update here. Thx

Hi <@U04KQBJJSHG>! Sorry you ran into this, it was an issue in the code that converts dbt config to FreshnessPolicies (so it was not just a UI issue). It's a simple fix, and will go out in next week's release.

If you're interested in resolving this faster, it is possible to pass in a custom `node_info_to_freshness_policy_fn` parameter to your `load_assets_from_dbt...(...)` call. In this case, you could just copy the code from this PR: <https://github.com/dagster-io/dagster/pull/12904> :slightly_smiling_face:

Otherwise, next week's release will have the fix enabled.