Clockwork VS Montrose

https://github.com/Rykian/clockwork always worked well when I have used it in the past.

Unless you have very specific requirements that preclude this, you might want to run this task as a background job (e.g. Sidekiq worker) instead of as a rake task. This is a little bit of an opinion. There isn't one right way (indeed, that's one of the best things about Ruby). But in my career I've usually seen rake tasks used for things that need to be performed infrequently, and not as part of normal system operation. For things that need to be performed at regular intervals, and are part of the normal operation of the app, I usually see them set up as scheduled background jobs. You can use a background job gem (Sidekiq is wildly popular; Resque is another good one) and combine it with a scheduler (I'm personally a fan of the Clockwork gem but there are others out there).

Hi I've got a project which requires normal one off events, as well as recurring events. Looking at the resources available it seems like there are really just three gems available(montrose, recurrence and ice_cube). Of the three I've had the best results with recurrence because it allows me to pass a hash of arguments to the schedule builder. As well as handling exceptions which montrose doesn't seem to offer.