Wednesday, May 23, 2012

Batch CronJob Operations

Updated: This feature is added again with more improvements!

Hello there,

SetCronJob now supports Batch CronJob Operations, including Delete, Disable multiple cronjobs at once.

To do this, simply click on the the cronjobs' row (the row will then be marked as selected, and the checkbox at beginning of row is checked), then select desired operation.

You can also check the first checkbox at header row (before ID column), this will select/unselect all cronjobs at once.

More batch operations will be added if necessary.

If you have any suggestion, just let us know :-)

Friday, May 18, 2012

Please resend your email!

Hello there,

After moving the server, we forgot to forward the emails via Contact form to our support mailbox, so your messages weren't received.

If you tried contacting us via Contact form within last 5 days, please resend your message, and we'll happily reply asap :-)

Monday, May 14, 2012

SetCronJob Moved Server and Changed IP

Hello all,

Recently, our server had performance problem, which caused high server load, slow website speed, slow database queries.

We worked with KnownHost but couldn't find out problem and solution.
(They did help, and also reinstalled the server, but it not worked as expected).

So, we moved the whole site to a new server, and ended up at Linode.
SetCronJob is now stable and fast.

Response time before and after the server moving - from Pingdom monitor

We tried our best to make the moving flawless, but troubles were unavoidable, and sometimes you may see SetCronJob was inaccessible, or showed error message. Some cronjobs failed (with message "Cannot assign requested address") or didn't run.

Before the problem occurred, we already made an assurance: if SetCronJob has downtime and couldn't execute cronjobs, when it's up again, it'll run them once.
This is useful when we're facing downtime: if your daily backup cronjob couldn't run at 0:00 due to SetCronJob down, it'll run later e.g. at 0:03, so at least it runs your backup.

If you white listed or granted only SetCronJob to run your cronjob, please update our new IP:
Additional IP(s) may be added soon if necessary.

If you encounter any problem, or have any question, please comment below or contact us.

Tuesday, May 8, 2012

Cron Timezone: Set timezone for your cronjobs

Hello all,

I'm happy to announce that since May 2012, SetCronJob fully supports custom cron timezone for each cronjob :-)
This feature is greatly helpful when you want your cronjobs to execute under your timezone or any desired one.

Custom time zone for your cronjobs

How to choose custom time zone for your cronjobs:
Select custom time zone for your cronjob
  • Create new cronjob or edit your cronjob
  • At Cron Timezone, click on the box to drop down the timezone list
  • Select your desired timezone
  • Then Save CronJob.
That's it!

From now on, your cronjob will be executed under American/Los_Angel timezone (Pacific Time Zone, PDT - with daylight saving time, or GMT - 7).

For convenient, SetCronJob shows cronjob's timezone and current time in cronjob's Logs page
CronJob's timezone and current time displayed at Logs page

User Time Zone

You can also visit My Account tab and select your desired time zone.

Select user timezone for your account

This will set the default timezone for your new cronjobs :-)

Daylight Saving Time is supported

SetCronJob does support Daylight Saving Time (DST), where we move our clocks back and forth (Spring forward, Fall back).

It's useful when you'd like your cronjob to follow the time change in some nations/areas that observe DST.