https://dagster.io/ logo
Title
b

bobzoller

04/27/2021, 4:01 PM
if I delete a pipeline run with a given
run_key
is that enough to get the sensor to trigger again (assuming it yields that runrequest again)? (trying to resolve a situation where many pipeline runs that were triggered by a sensor failed -- with bad run_config -- and I want to re-trigger them all with the fixed run_config)
j

johann

04/27/2021, 4:03 PM
cc @prha
p

prha

04/27/2021, 4:39 PM
@bobzoller it depends on the sensor evaluation function…. If the sensor will yield the RunRequest for that run_key in the next tick, then yes, deleting the run should be sufficient
sometimes, though, people will write their sensor with an implicit cursor, to reduce the computation within the sensor evaluation function
then you might have to reset that value
b

bobzoller

04/27/2021, 4:41 PM
yup word. I haven't added cursors yet 👍
if I needed to in the future, is resetting that value digging into postgres?
p

prha

04/27/2021, 4:43 PM
yeah, but I’m actually restructuring some of the sensor cursor code right now. I’ll add a dagster cli command to manually reset the cursor (e.g.
dagster sensor set_cursor <sensor_name> <cursor_value>
or something equivalent)
:1000: 1
b

bobzoller

04/27/2021, 5:54 PM
nice. deleting the runs worked great, I'm all green again!
🙌 1
m

Ming Fang

04/28/2021, 5:26 AM
@prha please add ability to reset cursors in dagit also