Thursday, April 19, 2018

Missing cron executions

Hi there,

We received reports that multiple cronjobs executions were missed without any trace this morning.

It appears that one of our database servers stopped responding some time after our recent reconfiguration, while our health check script failed to detect and kept sending database queries to it. That's why some cronjobs didn't execute.

The problem was fixed and a new reliable health check script was added to prevent it from happening again. Your cronjobs should be working fine from now on.

I'm really sorry for the recent problems.

As a token of our apology, I have added a credit of 5% of your account plan price to your account balance.

If you encounter any problem with SetCronJob, please let us know ASAP.

Best regards,
Nguyen An Thuan.

Friday, April 13, 2018

8 new servers are added

Hello there,

SetCronJob just added 8 new servers and will be using them for processing your cronjobs. Please add their IP addresses to your whitelist as soon as possible.

Here are the new IPv4 addresses:
173.230.130.112
50.116.43.46
192.155.88.39
69.164.214.46
45.33.90.124
72.14.187.212
198.58.119.103
173.255.203.62

And here are new IPv6 addresses
2600:3c02::f03c:91ff:fe30:20bf
2600:3c02::f03c:91ff:fe30:208c
2600:3c03::f03c:91ff:fe30:204a
2600:3c03::f03c:91ff:fe30:20d4
2600:3c03::f03c:91ff:fe30:20ab
2600:3c00::f03c:91ff:fe30:97db
2600:3c00::f03c:91ff:fe30:979e
2600:3c00::f03c:91ff:fe30:97a2

You can view our full list of IP addresses at our Help Center.



If you want to receive email notification every time we add new servers, please subscribe here.

If you need any help, please feel free to create a ticket at the Help Center.

Thursday, April 12, 2018

Service outage on Apr 12, 2018

Hello there,

We had received multiple reports regarding the service outage from 5 AM this morning (UTC time). Unfortunately, we didn't react in time, and it caused our service down until 11 AM.

We checked and fixed our cron dispatching servers, and the service has been working fine since then. We replaced, upgraded and added more dispatching servers with the updated software to make sure this won't happen again. We also had our microservices monitored closely so we can react faster.

We already rerun your missing cron executions to make sure your important tasks are performed at least once today.

We are sorry for the inconvenience that caused.

As a token of our apology, we have added a credit of 10% of your account plan price (e.g. $5 for Platinum accounts) to your account balance.

If you encounter any problem with SetCronJob, please let us know ASAP.

Best regards,
Nguyen An Thuan.

Sunday, March 25, 2018

Send cron execution results to webhook URLs

You can now send your cron execution results to a webhook URL, so you can process it automatically in your callback script.

It's available in Diamond account only, and you can add it similarly to adding emails/Slack IDs at Account > Contacts.
Add webhook URL at Account > Contacts.
Please note that the timeout limit for webhook calls is only 10 seconds, so it's recommended to just store the results and process them later.

The execution result structure is similar to result in Cronlog data structure, except that it has an extra field: id as cronjob's ID.

Thursday, March 1, 2018

Two-Factor Authentication is supported

Hello there,

You can now protect your account better with our Two-Factor Authentication. When enabled, after logging in successfully with your email and password or with your social account, you'll need to enter another authentication code from your authenticator app.
Authentication code required before accessing your account.


To enable, visit Account > Overview, click Enable Two-Factor Authentication. You'll need to install an authenticator app first on your mobile phone or tablet. You can then scan the barcode displayed, and enter the authentication code generated by the app to confirm.

SetCronJob recommends Google Authenticator and Authy app.

To disable, visit Account > Overview, click Disable at Two-Factor Authentication section. You'll need to enter authentication code one last time to confirm. You may want to delete SetCronJob from your authenticator app too.

If you have any question, just let me know.

Friday, February 23, 2018

Power Failure in datacenter

Hello there,

This morning I got reported that SetCronJob had been down from Feb 23, 18:03 to 19:16, UTC. After some research, I found that the power failure in Fremont datacenter at Linode caused the issue. You can read more about the incident here.

Because all of our core servers (database, web, cron distributor, etc) are hosted in Fremont, they had crashed and stopped working entirely for more than one hour. With our current configuration, there was nothing we could do about it. We can only run the cronjobs with missing executions once to make sure they won't miss.

We are sorry for the inconvenience.

We are working on improving our system to prepare for incidents like this.

Thursday, January 4, 2018

Referral Progam

Hello everyone,

I'm eager to announce our Referral Program that will reward bonus credit to both the referrers and their friends. When someone signs up using your referral code and made a payment, both of you will get 20% bonus credit of the payment after 30 days.

To sign up for Referral Program, just visit Account > Referrals, click Get my referral URL and share it with your friends.

For more information, please visit our Help Center.

Monday, January 1, 2018

Community and Feature Requests at Help Center

Hello there,

You can now log in to SetCronJob's Help Center using your SetCronJob account. Just click Sign in button in the top right corner at the Help Center.

I also enabled the Community where you can discuss questions regarding your cronjobs as well as request new features. You can vote on existing feature requests. The more votes a request get, the faster it'll be reviewed and implemented to SetCronJob.

If you need any help, just submit a ticket to our help center.