Schedules
getOperate provides the same set of features as CRON, but with a user interface and control panels. It allows you to define Schedules for Scripts and Flows. Once a schedule is defined, the script will automatically run at the set frequency. Think of it as an easy-to-use scheduler similar to CRON that you can share with other users.
A Schedule consists of a Script or Flow, its arguments, a CRON expression that controls the execution frequency and an Error Handler to deal with failed scheduled executions.
Cron is a powerful and versatile tool that enables users to automate tasks by scheduling them to run at specific intervals or times. From automating routine system maintenance to sending periodic email reports, cron plays an indispensable role in streamlining processes and improving productivity for developers, system administrators, and even casual users.
However, as with any powerful tool, using cron comes with its own set of challenges and potential issues. Common problems associated with the use of cron include:
- Runs History: to maintain a record of script runs and log outputs through cron, you must manually incorporate that logic.
- Error Handling: in the event of a failed run, self-crafted logic is required for notifications (Slack, emails).
- Manual Runs: executing a cron job manually, outside of its schedule, proves difficult and can lead to inconsistencies due to potential environment differences.
- No UI: navigating cron jobs is challenging without a centralized hub, particularly for larger engineering teams. This comes with induced issues:
- Handling permissions and Errors among users and editors and
- Server downtime: when the server hosting the job experiences downtime, monitoring and alerting is problematic.
A bit of Context: How getOperate Works
getOperate is an infra to build all internal tools through code, such as UIs and workflows based on simple scripts (TypeScript, Python, Go, Bash, SQL).
Managing scripts, flows and apps on getOperate works at the workspace-level. Admins invite developers and operators to the workspace where are hosted workflows. The first two can write and edit flows as well as managing permissions, executions etc.
Cron jobs are one of many ways to trigger workflows in getOperate (among webhooks, auto-generated UIs, customized UIs, Command Line Interface, Slackbots etc.)
Configure Schedules for Each Task ( Script, Workflows )
From your workspace, navigate to the dedicated Schedules menu and select New Schedule.
-
Configure the schedule frequency using cron syntax or the simplified builder.
-
Fill in the arguments that will be used for the automation. The arguments are the ones of the given script or flow. If you want your arguments to be dynamic, you might want to use a workflow.
-
Optional: Add an Error Handler
-
Optional: Add a Recovery Handler
Click the Schedule button and you’re good to go! The schedule will be automatically ‘Enabled’. Toggle it off if needed.
Handle Several Schedules for the Same Workflow
The previous configuration can be replicated multiple times for the same workflow and therefore several schedules can work in parallel.
If the Schedules menu allows you to control future executions of scripts and workflows, you can check all past and future runs clicking on Runs. This will lead you to the Runs menu, with a filtered view on your runnable.
… where you can get details on each run:
Configure Schedules from Flow Editor
The same method can also be done from the flow editor.
From your workspace, pick the workflow you want to schedule.
Go to the Schedule menu …
and either schedule in cron or in Basic mode that will automatically be translated in cron. Once it’s done, you can see in next picture that the cron expression is now visible on the toolbar.
Fill in the inputs, toggle the Schedule Enabled option, save, and you’re all set!
Schedule App Reports
Send a PDF or PNG preview of any app at a given schedule.
More at:
Schedule App Reports
Send a PDF or PNG preview of any app at a given schedule.
Control Permissions and Errors
Schedule Error Handler
From the schedule configuration, add a special script or flow to execute in case of an error.
For example, this can be a script that sends an error notification to Slack or Discord.
You can pick the Slack pre-set schedule error handler.
Schedule Recovery Handler
From the schedule configuration, add a special script or flow to execute in case of of recovery from Error.
You can pick the Slack pre-set schedule recovery handler.
Be notified every time a scheduled workflow has been executed
For scheduled flows, add a simple step to be notified about the execution of the scheduled flow.
In this example I chose to receive an email, but you can use other notification methods like Slack, Discord or any other other method your imagination and API calls can create.
Configure the email.
And watch your mailbox.
Given how flows work on getOperate, it means that once the previous step has been successful, the Email step will trigger.
Error handler If you want to handle failure and receive another message in that case, add an Error Handler to your workflow that will let you know if a failure happened at any step.
Manage permissions from the workflow
From the settings menu, change the owner to a folder (group of people) to manage view and editing rights.
The process is very simple but it will allow you to schedule tasks with confidence and get an aggregated view on them.
Not only can you build scheduled jobs from getOperate but also you can import all your existing scripts - as getOperate supports TypeScript, Python, Go, Bash or SQL - as did one of our esteemed users for their own scheduled jobs.
Schedule to run later
From a script or flow’s Run page (after being deployed), you can “Schedule to run later” to schedule the execution to a given time without being recurring.