Friday, December 1, 2017

Cron notifications to multiple emails and Slack channels

Hi there,

By default, SetCronJob only sends notification emails to your registered email address. From now on you can add more recipients for your cron notifications.

First, visit Account > Contacts to add your email or Slack incoming webhook URL.
Add contacts at Account > Contacts.
The targets must confirm to accept incoming cron notifications from SetCronJob.

Once a target is added and confirmed, you can update your groups to send all cron notifications to your contact(s). All cronjobs under that group will send their notifications to the contacts. You can add up to 3 different contacts per group.

To add and update a group contact, click Edit on a group and select desired contacts:
Select contacts when adding/editing groups.
When contacts are added to a group, you can see the icon next to group name like this:

Contacts icon in group headers.
You can hover over the icons to see the contacts name, or click on it to update contacts.

You can move your cronjobs into a group by editing it, at the section Name, group, and note, select desired Group value. You can also change when to get notifications for each cronjob by editing them, select a desired Notify me value, by default is Notify me: Only when cron is disabled because of failures.

This new feature is available in Platinum accounts and higher, and Slack is supported in Diamond account only.

If you have any suggestion or question, just comment below or contact us.

Sunday, November 5, 2017

View full output in Platinum+ accounts


SetCronJob stored only first 4KB and last 1KB of your cronjob execution's output by default. The rest is truncated, and there was no way to retrieve it. It's a little inconvenient when you need the full output to diagnose your script or check error messages in between.

We'll now store up to 320 KB (first 256 KB and last 64 KB) of failed execution's output. At the Cron execution logs page, you can click the View full output button to see your full cron execution result.
Click View full output to see longer output (up to 1.25MB)
This feature is available to Platinum and Diamond accounts only. You can upgrade your account by visiting Account > Plan.

If you require any additional information, please do not hesitate to contact us.

Friday, October 27, 2017

SetCronJob API request now supports JSON

Hello there,

From now on you can send API request via POST with parameters in query string format or JSON format.

Query string format:
curl -d 'token=******'

JSON format:
curl -d '{"token":"******"}'

We also update our cronjob execution results data structure. In short, we moved most data into cronlog.result including startTime, executionTime, status, etc. For backward compatibility, you can still access those values at the moment, but it will be removed within 3 months. You'd better update your script to reflex those changes if any.

Wednesday, September 6, 2017

Share your account with other users

Update on November 26, 2018: Since Team Plan is now supported, this feature will be deprecated.

Wednesday, August 9, 2017

Set cronjob to run once a year

You can now set cronjob to run in a selected year. It'll be useful in case you want your cronjob to run only one time and not repeat in next years.

To select the year field, click Edit cronjob, click button Time settings next to When to call field, then select the Year value. The default value is Every year.
Select the year to run your cronjob in

Wednesday, July 5, 2017

Separated failed cron execution results

Hello there,

If you have a Gold account or above, you can see the separated failed cronjob execution results. We will store the latest failures so you can check it later at any time.

To view the failed results, just click on Logs button on any cronjob, then click Failed executions button.

Saturday, May 13, 2017

Retrying failed cron executions

A new feature has been added for Platinum and Diamond account. SetCronJob now can automatically retry failed executions. To update your cronjob, click Edit, at the section Detect failure, retry and notify you, update Retry and Retry after values:
Retry settings
You can set it to retry up to 10 times, after 1 - 60 minutes after a failed execution.

When a cronjob fails, it'll be scheduled to rerun manually after X minutes, again and again until it's okay. This still counts in the total failures, so you should also increase the Failure threshold to a bigger value.

It helps in temporary problems (e.g. your website is down or unreachable in a few minutes) and retrying later can fix it. If your cronjob fails persistently, you should check and fix it yourself.