Schedule tasks x timeunits after previous task has finished

[mr-flannery]

I'm submitting a...

[ ] Regression 
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

From my understanding of the docs, there are currently three styles of scheduling supported: cron, interval and timeout-once.
None of them are what I would like to do, which is...

Expected behavior

...interval after last task finished. Essentially something like "run a new task 10 seconds after the previous task has finished".

What is the motivation / use case for changing the behavior?

For example, I have a task that should regularly poll something, let's say every ten seconds.
In these ten seconds, there could be very few or a lot of new things that I'm polling. If there are lots of new things that I need to process, this might take longer than the specified timeout. Ideally, I'd like to prevent my task from starting while the previous task is still running.

[kamilmysliwiec]

You should use dynamic intervals/timeouts/cron jobs for that https://docs.nestjs.com/techniques/task-scheduling#dynamic-intervals