Absolutely critical to be able to impose rate limiting, not only for static journeys but also for recurring journeys. In the case a user were to specify a journey to recur faster than the journey can complete, then terminate the previous run before the journey recurs. Perhaps some sign-posting to users to ensure they consider the interaction between the timing of the rate limiting and the timing of the recurrence.