← Back to EasyCron.com

Jun 11, 2014

Free Trial Plans Added

From now on, all EasyCron premium plans are triable!

We launched 3 Trial plans (Starter Trial, Plus Trial and Max Trial) for Starter, Plus and Max plan. They're totally free. No credit card information or prepayment will be asked before using these plans.

We believe that the Trial plans are the best way for new users to test drive all the cool features which EasyCron has.

Currently all Trial plans last for 7 days. That will be more than enough for anybody to evaluate if EasyCron works for them.

Try our free Trial plans for our cron job service now!

Apr 17, 2014

EasyCron moved to https

In order to better protect our users' data, EasyCron switched to HTTPS today.

Using secure connection will be default over our whole site. Any HTTP connection to us will be redirected to HTTPS with 301 permanent redirect. There is one exception though: any requests to our API will be kept intact. The HTTP API requests begin with "http://www.easycron.com/rest/". This execption assures that any requests made by existent applications will still work. New API implementation is encouraged to use our HTTPS endpoint.

After the switch, all data transferred between users' browsers and EasyCron server will be encrypted and immune to sniffing.

If you're our affiliate partner, please update your affiliate link accordingly. Although updating the link is not necessary for us to track your referring, it's better to avoid a redirect :)

Enjoy a more secure EasyCron, and write to us if you want a talk :)

Feb 27, 2014

Cron job execution statistics and separate failure logs added

In order to help users inspect the execution status of their cron jobs, we added cron job execution statistics and separate failure logs to EasyCron.

You may see the cron job execution statistics (including the total number of successful executions (TS), total number of failed executions (TF) and number of consecutive failed executions (CF)) in the cron job list:


Cron job execution statistics

If there is non-zero "total failures" in any of your cron job rows, the background color of the number will turn red. You should check these outstanding rows immediately to resolve the potential problems.

Besides the general Logs and Predictions, we implemented a feature that keeps failure logs separately from the general logs. With this feature, you can analyze the logged failures at any time, and have no need to worry about the "flowing away" of the oldest logs.

For existent cron jobs, we started logging the execution statistics and separate failures from Feb 27 2014 13:19:00 UTC. Please keep in mind this point when evaluating your cron jobs' health.

Below we list how do the user behaviors affect the logs and statistics data.

Change Settings Enable Log Disable Log Enable Cron Job Disable Cron Job
General Logs Clear Clear Clear - -
Separate Failure Logs Clear Clear Clear - -
Total Success Count Reset Reset Reset - -
Total Failure Count Reset Reset Reset - -
Consecutive Failure Count Reset Reset Reset Reset -

In above table, "Clear" means deleting all logs; "Reset" means changing the number to zero; "-" means doing nothing.

"Change Settings" includes any actions that can change cron job settings excepting "Enable Logs", "Disable Logs", "Enable Cron Job" and "Disable Cron Job".