Skip to content
FastCron

FastCron Changelog

You can receive monthly product updates from FastCron by subscribing on the Profile page.

You can email me at support@fastcron.com to suggest a feature.

August 2026

Issues

When your cron job fails more than a certain number of consecutive failures, an issue will be created. FastCron will track the issue starting time, total duration, and the cause of the error. The ongoing issues will be displayed on the Cron Jobs page (start page), and on each cron job’s Logs page.

When your cron job succeeds 2 consecutive times, the issue will be closed. When you disable the cron job, the ongoing issue will be closed too.

Check for a keyword in the output

FastCron will check your cron job output for a keyword (e.g., success) when you enter it into the Output must contain field in the HTTP settings section. If the keyword is not in your cron job output, the cron job execution will be marked as failed.

Success HTTP status

You can now add success HTTP status to your cron jobs. By default, FastCron only accepts HTTP status 2xx (200 OK, 201 Created, 202 Accepted, 204 No Content, etc…), 504 Gateway Timeout, and 524 A Timeout Occurred. If you expect another HTTP status code, you can add it to the Success HTTP status list in the HTTP settings section.

July 2026

Content-Type header

If you add your own HTTP header Content-Type, FastCron will not add Content-Type again. See What HTTP methods are supported.

Retry failed connections

When FastCron couldn’t connect to your server, it will automatically retry once. You can now see two attempts on the Logs page, with #1 shows the first attempt result, and #2 shows the second attempt result.

June 2026

Last runs

FastCron will show the last 10 execution statuses (success: green, failure: red, warning: yellow) on the cron job dashboard. You can now see which cron jobs are having issues at a glance.

May 2026

API authentication

You can authenticate your API requests by including the HTTP headers Authorization: Bearer API-TOKEN. Passing the API token in the GET query is deprecated.

Dark mode

FastCron will switch to dark mode automatically to match your device settings. You can also enable it manually by clicking the moon icon next to your profile avatar.

API function update

When calling cron_add and cron_edit, you can add run and payload to run your created/updated cron jobs. This will save you a cron_run call.

cron_group_edit is removed.

April 2026

New theme

FastCron now uses a fresh new theme from Tabler.io. There are some small changes here and there, like clicking on the cron job URL will open its Logs page instead of Edit page. If you encounter any issues with the new theme, please email as soon as possible.

Stop disabling failed cron jobs

In the Pro plan, cron jobs will not be disabled after 50 consecutive failures. They will be retried forever with linear back-off. In the free plan, cron jobs that fails more than 50 consecutive times will be disabled.

Server region

You can choose a server region to process your cron jobs. Currently, only New York (old servers) and New Jersey are available.

March 2026

New servers

FastCron has added 2 new servers with new IP addresses to process your cron jobs. You can get the updated list here.

Please ask your hosting provider to add our IP addresses to their firewall’s whitelist.

Never disable failing cron jobs

In the free plan, FastCron will disable your failing cron jobs after 150 consecutive failures. Cron jobs in the premium plans won’t be disabled.

November 2025

Dedicated channel

You can now add a dedicated channel at Utilities > Notification channels. When adding/updating a channel, select Receive notifications from cron jobs with priority: None, select manually. After that, you can (batch) update your cron jobs, in the section Cron settings, select the Channel.

October 2025

You can now view the UTC time together with your local time on your cron job Logs page.

September 2025

You can now view the public status page at status.fastcron.com.

August 2025

cron_batch_edit removed

The API function cron_batch_edit has been removed. You should use cron_edit instead.

DNS cache removed

FastCron has stopped implement its own DNS cache. The resolved hostname will be stored in memory for up to 10 minutes and will be purged immediately if your cron job fails. No more stale IP addresses when your hostname updates.

Delete inactive cronjobs

Cronjobs that are inactive for 3 years will be deleted.

July 2025

Telegram cron notifications

You can now send /stop to FastCronBot to stop receiving cron notifications.

Cronjob statistic with timezone

Cronjob stats will be calculated based on its own timezone rather than FastCron’s server timezone (UTC).

June 2025

Opsgenie integration

You can now receive an alert in your Opsgenie account when your cronjob fails.

Slack/Mattermost integration

You can now also use your Mattermost webhook URL instead of Slack’s.

Account expiration

Your account will be downgraded to the free plan if applicable (less than 5 cronjobs). Otherwise it will just expire and all cronjobs will be disabled.

May 2025

Back off failing cronjobs

FastCron will back off failing cronjobs linearly. Learn more about cronjob failing and disabled.

January 2025

Cron logs bar charts

The cron logs chart of execution times is now shown by default. You can click on a bar to scroll down and view the corresponding execution result.

December 2024

Pushover.net integration

You can receive cron notifications on your Pushover.net devices. Copy your user key from your Pushover account, then add it on the Channels page.

Random delay

You can now add a random delay when adding/editing cronjobs. Click the Expression button and enter a delay time in minutes.

For example, you schedule your cronjob with cron expression 45 6 * * * and a random delay of 20 minutes. Your cronjob will run once a day from 6:45 to 7:05.

Schedule a maintenance

To pause cronjobs during a planned outage, you can schedule a maintenance. Your cronjobs won’t run during a scheduled maintenance period. Queued cron executions will be rescheduled to run after maintenance ended.

November 2024

Cronjob vs group priority

A cronjob can have a different priority than its group priority. Changing a group priority will only raise all its cronjobs to the same priority.

October 2024

Clean up

  • Old webhook URLs have been moved to the Notification channels.
  • The allowed groups of team members have been removed. They will see all cronjobs with the same or lower priority.
  • Group notification recipients have been removed. They will receive cron notifications from all cronjobs with the same or lower priority.
  • Stopped one-time cronjobs will be removed after 3 days.
  • You won’t be able to run disabled cronjobs using the API function cron_run.
  • Exports have priority too. Team members can view, download, delete, and import files with the same or lower priority.
  • Fixed: use Rn in the hour field in your cron expressions to select n random values.

POST data/payload validation

FastCron will now validate postData and payload. The POST data must be

  • Valid query string in the format name=value&name2=value2. No newlines are allowed.
  • If the postData/payload has newlines or starts with {, it must be valid JSON string.

Remove inactive account

FastCron will remove free accounts with no active cronjobs and no activity after 180 days. Due to the high rate of invalid email addresses and bounced messages, FastCron won’t send any notifications before removal.

September 2024

Variables

You can now add variables on the Environment variables page.

Use __variable_name__ in the cronjob URL, POST data, or payload, and it will be replaced with the variable value.

It’s useful for secret key/token, API/authorization token, or configuration values.

Use it when you want to change it once and apply to all cronjobs.

Team members

Members and Viewers now can see other team members. All team members can choose to start/stop receiving cron notifications from the team account on the Members page.

Priority level

You can now set priority level for your cronjobs, groups, channels, and team members.

Free WordPress plugin

You can now install and activate our official WordPress plugin here. It will create a free cronjob running every 5 minutes to your wp-cron.php. Completely free, no registration required, just activate and done.

Jira integration

FastCron now supports Jira integration. FastCron will trigger your automation rule with incoming webhook trigger. You can then add an action to process the notifications: send emails to team, create a new issue, or comment on an existing issue.

Search in cron_logs and cron_failures

You can now add keyword to cron_logs and cron_failures function to search in logs output, error message, and execution time (Unix timestamp).

August 2024

Disabled cronjobs won’t run

In 2 months (after October 20, 2024), you can no longer use cron_run to run disabled cronjobs. You need to edit the disabled cronjobs, select When to call: Manual, then Save and Enable them.

Cron expression manual

You can now create cronjob to run manually by selecting When to call: Manual or set the expression to manual. Use it to:

  • Run cronjob manually only when necessary
  • Create an endpoint URL for one-time executions
  • Create chained cronjobs: run this cronjob only after another cronjob complete (edit cronjob > Notifications, at Run cronjob, select the manual cronjob).

cron_run with time and payload

You can now set both time and payload when calling cron_run function. It’s great for running one-time cronjobs programmatically.

This is the recommended way to run one-time cronjobs.

Note: In 3 months (November 18, 2024), a one-time cronjob will count as one regular cronjob. Please update your script to use cron_run instead of cron_add before that day.

cron_next API function

A new API function has been added. cron_next will return an array of next execution times.

Telegram integration

You can now receive a Telegram message from @FastCronBot when cronjobs fail/succeed.

SSL certificate expiry dates

FastCron will monitor your SSL certificate expiry dates for your active cronjobs. You can view the SSL cert expiry dates on the Hosts page.

July 2024

Unlimited team members

You can now add unlimited team members to your account, even in the free plan!

Cronjob statistics and monthly report

FastCron has started collecting cronjob statistics (total runs/failures, average execution times, total 4xx/5xx responses) since July 15. You can choose to receive monthly reports on your profile page.

June 2024

Notification channels

You can now add account-level notification channels including Slack, Zenduty, Discord, Teams, and webhook (JSON payload). Once added, all failure/success notifications will be sent to your channel(s).

You can disable or delete a channel in case you don’t want to receive further notifications.

FastCron will show the last error message when failing to send notifications to your channel. We will automatically disable your channel after 5 consecutive failures.

Removed daily execution limits

The base cronjob interval is 1 minute. You can create cronjobs to run up to every 10 seconds, but they will count as 6 cronjobs.

Updated cron_run

You can now run your cronjob at a specific time using cron_run with time parameter.

May 2024

  • You can now change your referral code.
  • Help center have been moved to Docs.
  • API endpoint is now https://www.fastcron.com/app/v1/
  • Custom HTTP headers are now available in the free plan.
  • Show last 25 execution results for the free plan (from 10 results).
  • User avatars are now synced from your Google account.
  • You can now add your company/team name.
  • Contact email has been removed. Existing contacts have been converted to team members with role Viewer.

December 2023

  • You can prevent overlapping or allow up to 5 overlapping executions by adjusting the Max instances settings.