19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Hi team, trying to understand more on how the run_...
# ask-communityh
Hebo Yang
06/06/2023, 9:45 PMHi team, trying to understand more on how the run_status_sensor works. We have @run_status_sensor(run_status=QUEUED) but it seems to get skipped even when there were jobs being queued between its tick
Hebo Yang
06/06/2023, 9:49 PMi.e. The sensor skipped past 3 ticks from 2:06 to 2:37. However, we see that there are jobs being queued around 2:11.
y
yuhan
06/07/2023, 3:06 PMwhat’s the record_id for the run that got queued? one hunch could be as at record_id cursors were at 95629203, 95629334, 95629453, the run status sensor might have missed that queued run somehow.
h
Hebo Yang
06/07/2023, 4:10 PMThanks @yuhan! What’s the easiest way to get the record_id for a run please?
Hebo Yang
06/08/2023, 7:03 PM@yuhan following up on this 🙏
y
yuhan
06/08/2023, 9:38 PMsorry! looking now
yuhan
06/08/2023, 9:39 PMwe don’t surface that through the UI but you can get it through
DagsterInstance.get_run_record_by_id(run_id)👍 1
yuhan
06/08/2023, 9:40 PMthe record_id is auto incremented so that would help to determine when and which runs the run status sensor skipped
h
Hebo Yang
06/08/2023, 9:41 PMThanks. Let me try it. Another question, is there a way to see the job run for these sensors?
y
yuhan
06/08/2023, 9:42 PMby job run, did you mean the skipped runs, or the sensor body?
h
Hebo Yang
06/08/2023, 9:42 PMthe jobs that are triggered by the job status sensors
y
yuhan
06/08/2023, 9:45 PMto clarify, does your run status sensor kick off any new runs? — in most cases it should be listening to any skipped runs (run_A) and do something in the sensor body (in my_run_status_sensor), such as:
Copy code
run_A -> my_run_status_sensoryuhan
06/08/2023, 9:48 PMif my_run_status_sensor did react to run_A, in run_A’s log, you should be seeing something like:
Sensor … acted on run status ... of run ...h
Hebo Yang
06/09/2023, 10:29 PMMy run status sensor doesn’t kick off any new runs. We only want it to monitor job success/fail and emit metrics for now.
I just realized that the run status sensor directly executes the job inside our server pod instead of creating a dagster job to execute the code inside it. Is it the case?
8 Views