BeyondCron makes it easy to schedule database SQL queries and updates.
A familiar environment
When scheduling jobs within BeyondCron, group properties make setting a familiar, and consistent, environment a breeze.
A day at the races
Month calendars and schedules, make scheduling a day at the races a sure bet.
Once in a blue moon
Using date schedules makes executing infrequent jobs a breeze.
Ensuring that jobs aren’t missed when daylight savings starts is simple with trigger jobs.
Sometimes jobs fail unexpectedly. When this happens, BeyondCron makes it easy to see what, if anything, changed.
Often simple tasks require a script to be written, deployed and scheduled. BeyondCron allows such scripts to be embedded within the job.
Let's make a date
BeyondCron makes it easy to insert dates into jobs. Not only can dates be formatted to meet any requirement, they can also be adjusted forwards or backwards.
Often when scheduling a command, it does not always run as expected, typically due to differences in execution environments. To address this problem, BeyondCron can now echo the execution environment of a job.
When executing jobs, as well as logging the output of each job, BeyondCron now also records how each job was started, and also if killed, who killed it.
Control built in
BeyondCron is built from the ground up with controls in place to support the separation of duties, teams and environments.
Email jobs & wildcards
Email jobs with wildcard triggers, makes job monitoring simple.
The dashboard within BeyondCron allows jobs to be created, controlled and visualised from a single location.
BeyondCron allows jobs to be triggered externally.
As well as logging the output of jobs, BeyondCron also logs the execution status of each job execution.
When executing jobs, BeyondCron records the output of the job, which it then makes available via the command line and web interfaces.
Visual job flows
BeyondCron job flows can be displayed as a network, that updates in real-time as jobs are selected, executed and change state.
Whilst the BeyondCron allows for jobs to be created and modified interactively using the job panel, it also allows for groups of jobs to be imported and exported as JSON or YAML.
Enabled, bypased & disabled jobs
Jobs in BeyondCron can be either enabled, bypassed or disabled.
Schedules, triggers & conditions
BeyondCron has three methods for initiating the execution of jobs, which can be used separately, or in combination.
Along with cron, BeyondCron supports a collection of other schedule types, simplifying the creation of standard schedules, as well as providing new scheduling options that would be impossible to define using cron.
Easy to read times
BeyondCron uses easy to read times, such as “Today 09:17:00”, instead of "09/02/2016 09:17:00” for dates between yesterday and the next 7 days.
BeyondCron supports sunrise/sunset scheduling, which can be used for example to turn on security lighting at sunset, and off again at sunrise. As with all BeyondCron schedules, sunrise/sunset schedules adjust automatically for daylight saving time.
BeyondCron supports webhooks, which can be used for example to create Slack messages, or initiate Zapier actions.
BeyondCron natively supports timezones at the job level, ensuring that jobs execute as expected irrespective of server location.
When two or more BeyondCron servers are started, they automatically form a cluster, providing not only high availability, but also horizontal scaling. Horizontal scaling ensures that BeyondCron does not no become CPU or memory constrained as the job list grows.
When two or more BeyondCron servers are started, they automatically form a cluster, providing high availability as well as horizontal scaling.
A powerful feature of BeyondCron is the ability to separate a jobs definition from its scheduling. Rather than executing jobs at specific times, or intervals, as is the case with cron schedules, calendar scheduling executes jobs on the boundaries of calendar events.