You can receive monthly product updates from FastCron by subscribing on the Profile page.
You can email me at [email protected] to suggest a feature.
You can now customize your status page with your website logo and favicon.
You can now tag your cron jobs in the Cron settings section.
Separate multiple tags with commas (,), e.g. production,email,report.
You can also set your notification channel (Slack, Discord, etc.) to send notifications to tagged cron jobs only.
For example, if you want to receive Slack notifications for production cron jobs,
tag your cron job production, then tag your channels production too.
You can now create a public status page to show your current status / uptime. Keep your team members and customers informed with real-time status update.
You can also use a custom domain name for your status page.
Simple setup: add a CNAME record pointing to statuspage.fastcron.com, and we will handle everything else.
Free SSL certificates are provisioned and renewed automatically.
Tip: You can add a cron job to your website URL to monitor its uptime. When your website is down, FastCron will notify you via emails and other configured notification channels like Slack, Discord, Telegram, webhook, etc.
FastCron will verify your SSL certificates when running your cron jobs. If your website SSL certificate is expired, invalid, or unable to be verified, your cron jobs will be marked as failed, and you will receive notifications.
If you're using self-signed certificates, you can turn off Verify SSL certificate in the HTTP response section.
FastCron will now consider executions with Timed out errors as failed. After two consecutive failures, your cron jobs will be marked as DOWN, and you will receive notifications.
You should either increase the Timeout limit in the cron job settings or update your scripts to run within the time limit.
This applies to newly created cron jobs only (with ID from 21,100,000). Existing cron jobs won't be affected.
You will now receive reports with your cron jobs status every week. The report will be sent every Monday, and the stats are from Monday to Sunday in the last week.
You have to keep your free account active by logging in at least once every 90 days.
You will receive an email when you haven't logged in for 90 days. 30 days after the email, your cron jobs will be disabled.
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.
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.
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.
If you add your own HTTP header Content-Type, FastCron will not add
Content-Type again.
When FastCron can't connect to your server, it will retry at 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.
FastCron will show the last 10 execution statuses (success: green, failure: red) on the cron job dashboard. You can now see which cron jobs are having issues at a glance.
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.
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.
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.
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.
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.
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.
You can now view the UTC time together with your local time on your cron job Logs page.
You can now view the public status page at status.fastcron.com.
cron_batch_edit removedThe API function cron_batch_edit has been removed. You should use cron_edit
instead.
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.
Cronjobs that are inactive for 3 years will be deleted.
You can now send /stop to FastCronBot to stop receiving cron notifications.
Cronjob stats will be calculated based on its own timezone rather than FastCron's server timezone (UTC).
You can now also use your Mattermost webhook URL instead of Slack's.
Your account will be downgraded to the free plan if applicable (less than 10 cronjobs). Otherwise, it will just expire and all cronjobs will be disabled.
FastCron will back off failing cronjobs linearly after 100 consecutive failures.
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.
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.
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.
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.
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.
cron_run.FastCron will now validate postData and payload.
The POST data must be
name=value&name2=value2. No newlines are allowed.
postData/payload has newlines or starts with {, it
must be valid JSON string.
FastCron will remove free accounts with no active cron jobs 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.
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.
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.
job_show and
cron_failuresYou can now add keyword to job_show
and cron_failures function
to search in logs output, error message, and execution time (Unix timestamp).
manualYou can now create a cron job to run manually by selecting When to call: Manual or set the
expression to manual.
Use it to:
cron_run with time and
payloadYou 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 functionA new API function has been added.
cron_next will return an array of next
execution
times.
You can now receive a Telegram message from @FastCronBot when cronjobs fail/succeed.
FastCron will monitor your SSL certificate expiry dates for your active cronjobs. You can view the SSL cert expiry dates on the Hosts page.
You can now add unlimited team members to your account, even in the free plan!
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.
You can now add account-level notification channels including Slack, 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.
cron_runYou can now run your cronjob at a specific time using cron_run with time
parameter.
https://www.fastcron.com/app/v1/Need help? Reach out to [email protected] - we're happy to help.
See why 8,000+ website developers and their teams use FastCron to run their cronjobs 12 million times a day.
The reliable online cronjob service for your websites since 2009.