hello, i noticed something odd this morning - I started two runs that materialize separate dbt assets from the same project at around the same time (this was manually, so there was a few seconds difference between them). One of them went off without a hitch (lets call this run X) but the other one (run Y) yielded warnings of the form

Materializing unexpected asset key: AssetKey([a,b])

where

a,b

is an asset from run X! Also, while asset materialization events for run X were successfully logged, there were no such events for run Y even though the logs indicate that the dbt job was successful. I notice that the run has

isolation:disabled

so i suspect this has something to do with it - any advice on what happened and how to prevent it from happening in the future?

hey @Leo Qin can you reproduce this error? Does running with

isolation:enabled

fix it?

trying it again without isolation... can you direct me to

https://docs.dagster.io/dagster-cloud/deployment/serverless#run-isolation depending on how you're launching the run you can either toggle the "isolate run environment" checkbox or add

non_isolated_runs:
  enabled: True

to the deployment settings

ok, so the retry without isolation actually failed... the failed run

unexpectedly exited with exit code -9

hmmmm is there a stack trace you can share?

yeah, dm them?

sure!

@Joe - starting the two runs with isolation lead to successful runs, and the outputs look correct as well.

nice Ill followup with why the non-isolated fails

ah - thanks for the followup. that makes sense!