New Version EasyCron.com Rolled out

Today we proudly rolled out a new version of EasyCron. It's a big update to many components of the system, including:

• New Design

  We replaced the old design with a fresh and inspiring new design. The change covers every pages and elements of the system. We believe you will be pleased with it.

• More AJAX

  We utilize more AJAX in cron job management process. You will notice that cron job management (enabling, disabling cron job, etc) is much easier than before.

• Bulk Actions

  Bulk Actions were requested by our users for many times. I need to say sorry about keeping them waiting, but we want to think over it thoroughly before building it :) Now it's done. I think the bulk action list shown below have covered most of the frequently used actions. If there is action we missed, let me know.

  
  Handle multiple cron jobs quickly

• Better Notices

  Some users may find that JS alerts are not that user-friendly, especially when these alerts are popped up with browser's "preventing these messages to show again" confirmation. We also see that. So we use light boxes and AJAX in-page notices in some cases this time.

• Responsive Design

  We attempt to pull-in responsive design to facilitate mobile users' using. Considering more and more users are connecting to EasyCron via cellphone, responsive design is a must. The responsive design is not implement on all elements throughout the site, if you have any advice, contact us.

• Google Custom Search Integration

  From now on, users can search our site conveniently via a Google custom search box added on the navigation bar. The search engine can search all public pages of EasyCron including FAQs, ToS, general pages, etc.. We hope it will save your time on searching information on our site.

• Page Row Settings

  For user who has huge number of cron jobs, we add a helpful feature to achieve better cron job navigation. This new feature is allowing user to custom the row number that each page of cron jobs has.

That's all. If you have any suggestion, send us a message.

Thanks for reading!

EasyCron.com Team

Cron job number limit removed

After deep investigation, we found that abuse mainly came from API, so we decide to remove the number limit on cron job, and keep the limit on API request, but adjust the quota to:

Free: Max 100 daily API requests
Starter: Max 1000 daily API requests
Plus: Max 2000 daily API requests
Max: Max 5000 daily API requests

Hope that our users will enjoy the change, you can set up unlimited cron job again now!

Service plans updated

We recently updated our service plans for the purpose of optimizing our system performance, improving stability and fighting abuse.

Two main updates to our service plans are:

1. Adding cron job quota to each plan as following:

Free: Max 5 active cron jobs
Starter: Max 50 active cron jobs
Plus: Max 200 active cron jobs
Max: Max 500 active cron jobs

2. Adding API request daily quota to plans as following:

Free: Max 10 daily API requests
Starter: Max 200 daily API requests
Plus: Max 400 daily API requests
Max: Max 1000 daily API requests

You may see details of these updates at https://www.easycron.com/pricing.

Good bye reCAPTCHA!

Since reCAPTCHA is becoming harder and harder to distinguish (actually sometimes it's ridiculously over blurred), so we take it down from the sign up page.

Now we have a cleaner and enough safe CAPTCHA at https://www.easycron.com/user/register.

Haven't use webcron yet? Try our free cron jobs service!

Let user decide to test the URL first or not before adding a cron job

From now on, EasyCron.com allows user to decide if to test the URL first before adding a cron job. In those cases which a user only wants to run his URL at configured time, this feature is very useful.

Usage:
In order to let EasyCron test the URL first, either clicking "ok" when EasyCron prompts the confirmation "Do you want EasyCron to test your URL first? (Recommended)" (in AJAX setting mode) or checking "Allow EasyCron to test the URL first" checkbox (in classic setting mode) will do the trick.

Don't want EasyCron to test the URL first? just do the converse.

Testing the URL first will find the timeout issue or script errors in early stage, so we highly recommend you allow us doing so.