We've got a bunch of scheduled processes that need to run at different intervals. It has been very easy to set up with CTG.

I've tried other cron solutions on Heroku and they were pretty clunky to set up. Cron to Go is super easy to use. Essentially no config required.

It created a bit of an issue with monitoring since each cron job spins up a new dyno. We are currently creating 1000 dynos per hour and HostedGraphite doesn't cope well with that. (That's probably more of an issue with HG than CronToGo but it's the only con I can think of).

Heroku's free cron job manager "Heroku Scheduler" is not very flexible with the schedules and has no notification mechanism built in. Cron To Go came to the rescue with its flexibility.

The pricing tiers are based on the number of cron jobs and the price can really add up if you are running a complex enterprise system. Also, it will be nice to have Cron To Go as a platform-independent SAAS instead of being tied to Heroku.

It was an easy setup and scheduling of jobs for automation.

Limitation on parallel jobs is the BIGGEST limitation running all jobs.

it is easy and good

This tool is easy to use for PostgreSQL work

schedule job and set up envir as app in heroku both stg and prod environment

At first I wasn't sure why we had to pay to have a core functionality, but even if we were able to set up cron jobs the usual way in heroku, I would gladly pay for this service.

I don't like to have a separate service/log in to be able to manage the software, but the tokenized log in is perfect.

I like Cron to Go. It makes me automation tasks simple and it's also very reliable. Any failure we've had was due to our endpoint API that we're pushing data to.

Cron to Go is really easy to set up and use. I highly recommend it on this alone. The last thing you want to do when completing a project is hassle with setting up your automation environment.

Figuring out Cron time, but this really isn't a big deal. There are free Cron time conversion calculators out there.

Amazing, I'm running a script file every hour, (the final product will only need it once a day), but for now it checks if any users in my database have a person on file whose birthday is today and if a match is found it gets their timezone and requested time to be notified and sends them an email at the appropriate time with Courier's email API

After using Heroku Scheduler I absolutely love Cron To Go. The difference is really astonishing. Scheduler has no dashboard no nothing to help you, whereas Cron to Go has an amazing dashboard that is very easy to use and understand with a suprising number of very helpful features. Its cheaper and actually has decent documentation unlike most Heroku scheduling apps. I love it!

I would love to see timezones as an option for lower tier plans, it's a somewhat basic thing and I implemented it myself in the script file I'm running since it wasn't offered for the basic plan, but would be cool to have it.

It's the best way I know to run consistent jobs in Heroku.

I love that I can pretty much set and forget. The history keeps me informed as I hunt down what went wrong with any job's kick-off. Some of my history was missing once and their support and responsiveness was awesome!

Nothing really. I am considering upgrading to get the alerts and notifications for failed jobs. Eventually we will set up the API to make it even more integrated.

The user interface is powerful, and surfaces everything we need. The statuses are very clear, and it's an instant dashboard that can be reviewed immediately. I also like the translation of the cron schedule and the presets available for the non-tech savvy.

Not really a con as much as a callout - this product makes the most sense and yields the most power if you are comfortable with cron.

It integrates with Heroku easily so we can schedule tasks to run for our app daily.

Its UI could be a bit more clear on what is going on for each item.

We love Cron to Go and at this point it's an integral part of our software architecture.

The ability to run multiple jobs separately from our application has been crucial to our business. Setting up new jobs to run is simple and we have experience very few issues with the service overall.

We really have no issues with Cron To Go other than being able to customize exactly who receives what alerts/notifications for specific jobs.

Overall, I absolutely love Cron To Go. It's so much simpler than maintaining your own cron schedule, and for the price it really is a no-brainer.

The UI is extremely intuitive. I love the guidance you get when generating the schedule using the cron syntax.

We wanted our cron job definitions to live in our code repository, so we had the same history and review process as the rest of our code. We had to use the Cron To Go API to achieve this. It would be nice if this was a first-class feature.

Liked the product overall. Would recommend it to others as well.

We primarily use the product to schedule tasks such as deployment pipelines. The product is very easy to use and does the job that it is designed for perfectly well!

The UI for changing schedules should be made easier. Currently we use 5 tasks for different deployment pipelines. If I have to change the schedule for them, I have to go into each of them one-by-one and change the schedule. It would better to have a checkbox based selection of jobs for pausing, triggering and changing schedules.

I use it to automate scripts

It's easy to use for people without a strong engineering background. The UI is friendly as well. I haven't experienced any bugs so far.

None so far. No bugs or issues that I've encountered yet!

The setup for Cron To Go was incredibly easy. It has been reliable since Day 1 and is pivotal to the success of our app.

Not much to dislike here. I would really enjoy an easy Slack integration for failed jobs but the webhooks and emails for failed job notifications suffice for now.

Would recommend.

Easy deployment, has worked perfectly, lets me know when tasks fail.

The logs don't seem to load up, although that hasn't caused me any problems.

Easy to setup as an Heroku-addon. Reliable and allows for running one-time jobs and powerful scaling options.

Would be nice with a tier that's cheaper than the current bronze ($9/month) for scheduling a single job.

Been using a long running app that checks and runs a cron job at given times and this is much easier and I have more visibility into what is actually going on. I also love that I can run the jobs on an adhoc basis.

I wish the same account could extend across multiple Heroku apps.

Really simple and easy to configure and use. Reliable & flexible, with great notifications. It really allows us to focus on the work and not on technicalities. The support is amazing!!! super helpful and quick

nothing yet... it's a really great product!

It is easy to add a job and rerun jobs. I like that I can run a job and look at the logs all in the UI. I like that the slack integration was very easy too.

I would like better tolerance for failures. Like we have some jobs that fail once or twice but they run every minute or so. I would like to be notified only if they fail 3 times in a row.

Overall, great for startups that need proof of concept or MVP deployment

Really good for rapidly deploying small tasks that need to run routinely without too much hassle.

concurrent runtime can be complicated based on pricing plan.

We have a lot of jobs (more than 40) on our project, and it was essential to find a solution with enough flexibility that's easy to set up and especially to analyse the logs in case of issues.

Easy to set up. Easy to access the logs. And the possibility to migrate from different environments/servers is advantageous.

Probably a bit expensive when you need a lot of tasks per day.

It gets the job done.

It's integrated into Heroku. I would've just added cron jobs to the EC2 my site is running on, but that is not intuitive considering how much is abstracted away on the Heroku platform.

I have to sign in to my Heroku account and then navigate to Cron To Go through the Heroku platform because of (I'm assuming) how the SSO is handled. I can't just go straight to Cron To Go whenever I see a job failed, for instance.

The UI is very clean and easy to use. I love the simplicity of it

So far everything is working really well.

Very Good

Task manager for its simplicity and easy to use.

Of everything I've used, there's nothing I would change.