heya folks got a quick one, if someone has seen a similar issue by any chance. I’ve upgraded the fivetran-dagster packate to 0.17.10 and I’m fairly certain that as of that version, when a table doesn’t yield any data that ought to be synced between fivetran source and dest, dagster is unable to materialize an asset from that op and then returns an error in the following manner:

dagster._core.errors.DagsterStepOutputNotFoundError: Core compute for op "fivetran_sync_foo" did not return an output for non-optional output "fivetran_snowflake_bar"