19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
announcements
dagster-airbyte
dagster-airflow
dagster-bigquery
dagster-cloud
dagster-cube
dagster-dask
dagster-dbt
dagster-de
dagster-ecs
dagster-feedback
dagster-kubernetes
dagster-machine-learning
dagster-noteable
dagster-releases
dagster-serverless
dagster-showcase
dagster-snowflake
dagster-spatial
dagster-support
dagster-wandb
dagstereo
data-platform-design
events
faq-read-me-before-posting
gigs-freelance
github-discussions
introductions
jobs
random
tools
豆瓣酱帮
Title
h
Hebo Yang
03/15/2023, 5:04 PMHi team, I have some dumb questions please:
• What’s the difference between sensor status Requested vs Started?
• We customized the run key when a sensor triggers a job. When we manually trigger a job run via backfill or launchpad, I think the run key still gets applied. I am wondering where the magic happens though?
y
yuhan
03/16/2023, 5:03 AMWhat’s the difference between sensor status Requested vs Started?Started means the tick has started to evaluate whether or not to kick off a run, whereas Requested means a run has been requested to kick off (i.e. in the queue to be kicked off soon)
We customized the run key when a sensor triggers a job. When we manually trigger a job run via backfill or launchpad, I think the run key still gets applied. I am wondering where the magic happens though?mind sharing some code snippets for this?
h
Hebo Yang
03/17/2023, 4:36 AMThanks Yuhan. For sensor state What does it mean then if we got a bunch of historical sensor states stuck in “started”?
For run_key, within our sensor we have this
run_key = f"{self.job_name}:{active_date_str}:{upstream_hash}"
yield self._get_run_request(job, active_date_str, run_key)