what's the behavior of sensors and schedules when execution gets stalled? like if you have a sensor running every 30 seconds and execution takes >30secs? i can't find this covered in the docs

Hi Steve, by execution do you mean evaluation of the sensor, or do you mean execution of the pipeline resulting from a sensor evaluation?

the former - basically the process of generating a list of run requests

Ah, gotcha. We have it running in a loop in the same process, so the interval might actually be longer than 30 seconds, in practice.

so the thirty second gap between evaluations begins counting when an evaluation concludes?

Yes

got it, that helps a lot. thank you!

a successful evaluation (resulting in either a run request, or skip) will write a record to our tick history, and we make sure that the next evaluation is at least the specified minimum interval after that last tick