Creating a recurring routine

Create a routine when you want Cedros to repeat a defined workflow on a schedule. Start with one clear result, choose the steps that produce it, check who receives notifications, and turn it on when the saved setup is ready.

For example, a weekly routine could collect site analytics and pass them to a saved job that writes a short performance summary. The job must already contain the instructions for that summary; naming a routine “Weekly analytics summary” does not tell it what to do.

Before you begin

You need permission to edit routines, the data sources your workflow uses, and any saved jobs or scripts its steps will call. If the controls are unavailable, ask an administrator to check your feature access.

A Job is a reusable operation that a routine can call. Review its purpose and instructions before selecting it, and make sure it is enabled. If the job you need is missing, have your administrator prepare it before continuing. A job that uses AI also needs a working provider and model.

Custom routines need a notification destination. Have a connected channel available, or a teammate subscribed on their own channel. Choose recipients who should receive information about this workflow.

Each scheduled AI run can add to your AI usage and costs. Choose a cadence that matches how often the result is useful.

Create and name the routine

1. Open Routines in the admin navigation and select New routine. Cedros creates an Untitled routine draft and opens it.
2. Open Routine actions and choose Name & description….
3. Enter a clear Name and a one-sentence Description. For example, “Weekly analytics summary” and “Summarize site performance for our Monday review.”
4. Select Apply to return to the routine. You will save these changes with the rest of its configuration.

The routine's schedule and steps are shared across the site. Agree on the purpose and recipients before turning it on.

Build the steps in order

In What it does, select Add step. Give the step a useful Step name, then choose its Type and complete the fields it shows.

• Data call: choose the Data sources the following steps need. Select only sources relevant to this workflow.
• Job: choose the saved Job to run. Check the selection even if one is filled in automatically; a job marked disabled is not ready to run.
• Script call: choose an existing Script for a transformation you have reviewed. Use this when your workflow needs a scripted operation.

For the weekly analytics example:

1. Add a Data call named “Collect site analytics” and select Site analytics if it is available.
2. Add a Job step named “Write the weekly summary” and select the enabled job prepared for that purpose.
3. Read the chain from top to bottom. The data comes first, followed by the operation that uses it.

A useful instruction for that summary job is: “Summarize the supplied analytics for our weekly review. State the reporting period shown in the data, highlight meaningful changes, and identify missing information. Do not invent comparisons or figures.” Have that instruction saved in the job itself.

Steps pass their output forward. A data selection supplies information; it does not by itself define a summary or another finished result. Start with a short sequence before adding branches or more operations.

Check delivery and recipients

Review the Delivery card before saving:

• Runs shows the schedule you are configuring.
• Read it in, when present, identifies where the routine's output is available in Cedros. A custom routine may not show this row, so confirm what its selected job or script produces.
• Notifies shows the shared notification destination. Use Change or the channel picker to choose the intended channel. If a default is shown, check it rather than assuming the routine will ask again before sending.
• Notify me, when present, controls your own subscription. Set one up opens notification setup if you do not have a personal channel. Save pending routine edits before changing your subscription.

A notification is not always the complete output. Check both the run result and the destination where your workflow saves its work. Turning off Notify me changes your subscription; it does not stop the routine for everyone.

Set the recurring schedule

1. Beside Runs, select Change to open Schedule routine.
2. Choose a Cadence, such as Every week.
3. Set Time and, when shown, Day of week or Day of month.
4. Check Timezone and read the schedule summary. For the example, choose Monday at 9:00 in the timezone your team uses.
5. Decide whether to enable Catch up missed runs after downtime. Leave it off if late work would no longer be useful.
6. Select Apply schedule, then Save changes on the routine page.

Apply schedule changes the form; Save changes saves the routine. Check the saved schedule after saving. Monthly dates after the 28th are skipped in months that do not contain that date.

Use Custom cron only when you need a schedule the regular choices cannot express and can verify the expression. For a first routine, a daily or weekly cadence is easier to review.

Save, check, and turn it on

Save the completed configuration and resolve any error shown. A new routine stays off after saving; saving alone does not start recurring runs.

If you choose to test it, select Run now after saving. This performs the actual workflow, including its configured actions and notifications, and may incur AI charges. It can run a saved draft while recurring runs are off. Review the job's effects and recipients before using it.

Check Run history for the outcome and the information produced. Succeeded confirms that the run completed; still read the result to check that it meets your needs. A failed, skipped, or retrying run needs review before you rely on the schedule.

When ready, turn on the switch beside the routine's status. Confirm that it reads On, then check the saved cadence and next-run time when shown. Reopen the routine from All routines to confirm its saved settings.

After its first scheduled run, check Run history and the expected output or notification. An On status is not proof that a scheduled run has already succeeded.

If you cannot finish setup

• Save changes is disabled: there may be no unsaved edits, a request may still be loading, or setup or permissions may be incomplete. Read the notice on the page.
• The switch or Run now is unavailable: save pending changes first, then resolve any provider or delivery notice.
• No suitable job or script is listed: prepare the required operation before continuing. Selecting an unrelated job just to complete the form can run the wrong work.
• Saving reports a step or schedule error: correct the named field, save again, and check the saved configuration.
• The run finishes but nothing arrives: inspect the run details, notification destination, personal subscription, and the place the selected operation writes its output.

To prevent future scheduled runs while you investigate, turn the routine off and confirm the off status. This pauses future scheduling; it does not undo completed work.

For an unresolved issue, ask for help with the routine name, approximate run time, visible status, and error. Keep credentials and private output out of the support message unless they are needed and appropriate to share.