Gooood morning. I'd like to run an observable source asset job that is kicked off by a sensor in a non-isolated env. It's a really simple HTTP HEAD call that finishes in like 1 second. Is the correct thing to do to add the

tag

"dagster/isolated": "disabled"

to the

define_asset_job

that is passed to the sensor?

Our documentation for run isolation is here: https://docs.dagster.io/dagster-cloud/deployment/serverless#run-isolation. @Shalabh Chaturvedi can this be configured by using tags?

@rex thanks - I did find that documentation. It implies to me that I can change the setting for the entire deployment. As a dev, I know best what jobs are safe to run in the shared env (small jobs), and what needs an isolated env.

Hi Gabe, you should be able to add

tags={"dagster/isolation": "false"}

to the

define_asset_job

to make that job always run non-isolated. I'm going to verify this and fix our documentation.

Great! And it's definitely "false" and not "disabled"?

Unfortunately I just verified that this doesn't work because it is a system tag. Let me see if there's another way we can mark a job to always run non-isolated.

Copy that thanks

While you can't add the tag in the

define_asset_job

it does work in the

RunRequest

returned from the sensor itself. Eg - this worked for me:

@sensor(job=my_job)
def my_sensor():
    yield RunRequest(
        tags={"dagster/isolation": "disabled"},
    )

I'll try this. Thank you!

@Gabe Schine if this works would you mind opening a GitHub issue for us to document this? I've starred this thread for my future use but agree we should document

How would you recommend going about testing this? It looks like my only option might be to deploy to prod, since local dev doesn't do isolation the same way, and branch deployments disable sensors.

yea I am not surprised the UI is not necessarily aware of the manually set tag, but this does sound promising. Also confirmed the best way to test would be what you've done + a run in prod

Hi Gabe - we have also made a change to make this system tag editable: https://github.com/dagster-io/dagster/pull/11917. It should go out with the next release later this week. This will allow setting tag directly on the job.

Nice! That'll be a little cleaner than the current approach.