Hi team! Is it possible for the output of an

@op

be included in the

config_schema

of another

@op

. Backstory, I'm trying to write a sensor that runs a job when the timestamp is greater than the some value. However, the timestamp is the output of a.

@op

function. So, I'm a bit confused because the RunRequest has

run_config

but there wasn't a

config_schema

used. Any thoughts?

I’m not sure if you can include output of other operations in the config_schema. You could however write your op to take the output of another op as an input, or perhaps better here would be to define the output metadata as the timestamp and have the op work off of that. Does that help at all?

Hey! As Zach said, you can't include the output of an op in the config schema. If I understand correctly, the timestamp value that you're using to launch off the run of some op

b

is dependent upon an upstream op

a

? In that case, perhaps the best thing to do would be to include

b

and

a

in the same job, and then use a conditional output to decide whether

b

executes depending on what timestamp

a

produces: https://docs.dagster.io/concepts/ops-jobs-graphs/graphs#with-conditional-branching