19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Hey all! We're trying to run a job every 30 second...
# ask-communitys
Samuel Shi
07/10/2023, 7:33 PMHey all! We're trying to run a job every 30 seconds using a schedule, but we aren't sure if there's a good way to do this, since schedule only supports running every minute using cron. I thought about using time.sleep(30) in between two copies of the run request but that doesn't seem to be working. Any ideas would be much appreciated!
t
Tim Castillo
07/10/2023, 7:35 PMHave you thought about using a sensor to yield the run requests?
s
Samuel Shi
07/10/2023, 7:45 PMIs there a practical difference? We're just trying to trigger a run every 30 seconds external to any change
Samuel Shi
07/10/2023, 7:45 PMAnd how do we specify it to run every 30 seconds, or does it automatically do that?
t
Tim Castillo
07/10/2023, 7:47 PMSensors can be evaluated in sub-minute intervals. ex. 30 seconds. https://docs.dagster.io/concepts/partitions-schedules-sensors/sensors#evaluation-interval
s
Samuel Shi
07/10/2023, 7:53 PMGotcha. Thanks!
Samuel Shi
07/10/2023, 9:03 PMHow do I prevent the sensor from skipping and have it run 30 seconds regardless? It says it skipped because the run already exists for the requested key. The schedule version of this runs fine and is the exact same logic
t
Tim Castillo
07/10/2023, 9:05 PMYou can create another run key that's a random value (ex. a hash of the current epoch) per run
s
Samuel Shi
07/10/2023, 9:10 PMFantastic, thanks! I also see here that if you pass in a run key of None it will run regardless: https://docs.dagster.io/_apidocs/schedules-sensors
4 Views