Monday, November 26, 2018

Team Plan - Multiple User per Account

If you are working in a team or company and want to share your account with your colleagues, you can now upgrade to Team Plan.

To convert your account to Team plan, log in to SetCronJob, visit the Account tab, check the box Team support at the current plan (starred), then click Select, and click Update plan directly.
Add Team support to your plan
The current price for Team support is $4, $10 and $20 for Gold, Platinum and Diamond account respectively. So standard Gold accounts are at $20 / year, and Gold Team accounts are at $24 / year.

When your account plan is updated, you can add team member at Account > Members.
Add team member to your account
Your team member needs to sign up first at SetCronJob. They will have their own account, but they needn't pay, upgrade, or renew them to use your account.

Currently, all team members can access your account and cronjobs, including:
- Manage your cronjobs (including view, add, edit, delete, view logs, etc).
- View your account information (name, email, plan, payments, address, API token, etc).
- Make payment and change your account plan.
- Manage your account's contacts (email, slack, webhook URL).

However, they can NOT change your account name, email, password. Team member won't be able to see and update your account's members list either.

Only the account owner will be able to add (invite) or delete team members.

After your team members are added to your account, they can access your account by clicking their profile name (top right corner), then click Switch account.
Switch to shared accounts
They can click Access to enter your account and manage your cronjobs. Once they're done, they can switch back to their own account or just log out. The current working account is persistently stored, so one can only work on one account at a time, and they'll continue where they left off whenever they log in to SetCronJob again.

If you have any question, just discuss at our forum, or create a ticket.

Friday, September 21, 2018

Auto delete one-time cronjobs

Hello there,

Now you can save one API requests with our new feature: automatically delete one-time cronjobs after they executed.

First, create or edit a group and update the select box Automatically delete stopped (one-time) cronjobs after to the desired value. You may want to keep the executed cronjobs long enough so you can check its execution results later.
Auto delete one-time cronjobs
After that, just create all one-time cronjobs under that group, and that's it.

Once your one-time cronjobs executed, they'll be deleted automatically after the set time.

Friday, August 24, 2018

5 new servers are added

Hello there,

SetCronJob just added 5 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:
206.189.231.210

142.93.14.153
142.93.123.161
142.93.189.98
104.248.15.180

And here are new IPv6 addresses
2604:a880:400:d1::20f:1001

2604:a880:400:d1::86a:5001
2604:a880:400:d1::8e7:b001
2604:a880:800:c1::1c:7001
2604:a880:800:c1::76:e001

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.

Wednesday, August 8, 2018

Set cronjob to run command on your server using SSH

SetCronJob is a web-based cronjob service, and currently, you can only set cronjob with URLs to your scripts.

If your cron scripts only support CLI (command line interface), then you may use our free service at Clustermin to create a cron trigger. It requires that you can access your server using SSH connections.

You can create a free account here. You can add up to 5 servers in the free account, and it'll be more than enough for your case.

First, you'll need to connect your server to Clustermin. For setting up cronjob, you should enter the user that has access to your web folders (public_html, www, etc.) and uncheck the box Create user. No worry, it will install nothing but a public SSH key into your authorized_keys file so that it can connect your server securely using SSH key next time.

Secondly, make sure your command works fine. Click the Execute button, then enter the whole cron command e.g.
php /home/your-user/example.com/proj/app/console do:something
and make sure it works as expected.

Thirdly, when you're sure the command works, visit Script > Add a script to create a script with the command as contents. Remember to check the box This is a private script.
Finally, visit Trigger > Add a trigger, then select your newly created at Run script, and your connected server at On servers.

When the trigger is created, you can copy the trigger URL, and set cronjob with it.

At your desired time, SetCronJob will execute (pull) the trigger, and Clustermin will execute the command on your server.

Let me know if it works for you ;-)

Saturday, July 21, 2018

Multi-Datacenter High Availability for SetCronJob

Hello there,

After recent incidents with the datacenter SetCronJob hosted in, I decided to move all the main servers to another data center as well as work on multi-datacenter clustering.

The servers transfer and multi-datacenter setup were completed without any service downtime. Now SetCronJob fully achieved high availability that can withstand whole datacenter outages.

The clustering was done with great help from Clustermin, my developing service for server cluster management and automation. Setting up once and it'll run setup script, update firewall rules and configurations files in all servers and all clusters, whenever a new server is added or old server removed.

The current setup will greatly improve our service reliability, and hopefully, I don't need to inform you about any downtime again ;-)


Wednesday, July 18, 2018

Power outage in our data center

Hello all,

I'm sorry to inform that we had another power outage at our new datacenter (we migrated to another data center after the last incident). Because of it, our service was unavailable from 22:56 to 23:55:30 July 18, UTC time.

The service has been working fine since then.

I'm still working on our server clusters to prevent this from happening again.

Sorry for the inconvenience that caused.

If you encounter any problem with our service, just let me know.

Wednesday, June 20, 2018

Connectivity issues in our datacenter

Hello there,

Currently, our server provider has a problem with their datacenter in Fremont which SetCronJob hosts on. The whole service is down at the moment.

UPDATED: SetCronJob is online and working again. The total service downtime is about 2 hours 50 minutes.

Although I had no control over major issues like this, I relied too much on my server provider and didn't react in time to migrate the databases to another data centers. This cause unnecessarily longer downtime of the service.

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

If you have any question or encounter any problem with SetCronJob, please feel free to let me know.

Thursday, June 14, 2018

Cron log size increased

Hello there,

I have increased the maximum execution results archived for all account plans:
- Silver: From 10 to 20 execution results
- Gold: From 20 to 50
- Platinum: From 50 to 100
- Diamond: From 100 to 250

The update is free and automatically added to your account plan.

Sunday, May 27, 2018

View predicted/scheduled cron execution times

Hello all,

You can now view your cronjobs' scheduled/predicted execution times at Logs > Scheduled executions. We'll calculate minimum 10 executions, maximum 150 executions OR 1 day.

For example, a cronjob running daily, at random time (hour and minute) will have 10 scheduled executions as shown below:

A cronjob running every 10 minutes will have predicted executions as shown below:
The scheduled executions will be calculated every time you create, update, enable cronjobs. A scheduled execution will be removed each time your cronjob is executed.

It'll help you get a better understanding of your time settings.

Thursday, May 24, 2018

Duplicate cron executions

Hi,

Recently, we have been working on a new cronjob execution predicting and tracking system to make sure that it won't miss any cron execution, and can automatically resume the service even after a service glitch or downtime. If it's done correctly, it'll greatly increase the service reliability and usability, as you can also see when your cronjob will execute with its current time settings.

Unfortunately, I have deployed it prematurely without proper system update, and it caused multiple executions (because of the auto retry feature) and missing executions from May 24, 21:25 to May 25, 00:44 UTC time.

I have rolled back the update and everything works normally like before.

I'll double check the update and make sure to deploy it carefully step by step to make sure this won't happen again.
UPDATED: The bug was found and fixed and the update is released.

I'm really sorry for the inconvenience it caused. As a token of our apology, I have added a credit of 10% of your account plan price (e.g. $5 for Platinum accounts) to your account balance.

We also have more update and upgrade in the coming time, and we'll let you know via this blog.

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

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.