Scheduled Processes

How time-based automation is shaped — cadences, scope, surfaces.

Scheduled Processes in SGEN is the time-based counterpart to the trigger model. Where triggers respond to events, scheduled processes run on defined cadences — daily, weekly, monthly, or on a custom schedule. This page is the Reference definition of the schedule primitive.

What is this for?

Read this page when you want the structural definition of SGEN's schedule primitive — how cadences are shaped, what scope they apply at, and where scheduled-behavior outcomes surface.

Good use cases

• You are scoping recurring background work (backups, reports, notifications) and need the schedule model.
• You are explaining to a stakeholder how SGEN handles time-based automation.
• You hit a "did the scheduled job run?" question and want the model laid out.
• You are designing internal SOPs around scheduled-behavior monitoring.

What NOT to use this for

• Step-by-step schedule configuration procedures — open the relevant Guide.
• Per-release shipped schedule additions — open What's New or Changelog.
• Event-driven automation — open Trigger Model.
• Per-job procedures (specific backup config, specific report config) — open the relevant Reference (Backup-and-Deploy Automation, Reporting Automations).

How this connects to other features

• Automation Overview — parent Reference area.
• Trigger Model — sibling primitive (event-based vs time-based).
• Notification Logic — how scheduled-process outcomes become operator-facing notifications.
• Backup and Deploy Automation — schedule-driven backup category.
• Reporting Automations — schedule-driven reporting category.

Definition

A scheduled process in SGEN is a job that runs on a defined cadence. The schedule has three structural parts: the cadence (when the job runs), the scope (what site or account the job runs against), and the behavior (what the job does each time it runs).

The defining property is time-based. Scheduled processes do not depend on operator action or platform events — they run because the schedule reached its time.

Purpose

The purpose of this page is to define the schedule primitive as a Reference layer. It explains the cadence options, the scope model, and where scheduled-process outcomes become visible.

Scope

This page covers the schedule primitive at the Reference level.

The page covers:

• The cadence options the platform exposes.
• The scope model (per-site vs account-tier).
• Where scheduled-process outcomes surface.
• The boundary against trigger-driven automation.

The page does not cover:

• Per-step schedule configuration — Guides.
• Per-job specifics — corresponding Reference pages (Backup-and-Deploy, Reporting Automations).
• Per-release shipped schedule additions — What's New or Changelog.

Cadence options

SGEN supports four cadence shapes for scheduled processes.

Daily

A job runs once per calendar day at a defined hour. Daily is the most common cadence for backups, summary reports, and recurring health checks.

Weekly

A job runs once per calendar week on a defined day at a defined hour. Weekly is common for digest-style reports and review-cadence notifications.

Monthly

A job runs once per calendar month on a defined day at a defined hour. Monthly is common for billing-adjacent reporting and longer-window summaries.

Custom

A job runs on a custom-defined cadence beyond the standard daily / weekly / monthly options. Custom cadences are used sparingly — the standard options cover most operator needs.

Scope model

Scheduled processes run at one of two scopes.

Per-site scope

A job that runs against one specific site. Daily backups, per-site reports, per-site health checks all run at per-site scope.

Account-tier scope

A job that runs across the account portfolio. Multi-site rollups, account-tier billing automation, account-wide audit operations all run at account-tier scope.

Where outcomes surface

Scheduled-process outcomes surface inside operator-facing surfaces.

Notification surface

When the operator opted in (or when the schedule includes notification by default), Notification Logic delivers the outcome notification.

Module surface

The artifact the schedule produced — backup snapshot, generated report, audit-log entry — surfaces in the corresponding module.

Schedule status surface

The configuration panel for scheduled processes shows the per-job last-run timestamp, next-run timestamp, and current health.

Constraints and boundaries

Scheduled Processes is a Reference area for the time-based automation primitive. It is not a substitute for Trigger Model (event-based) or for per-job Reference pages.

Use this Reference for:

• Understanding the structural shape of an SGEN scheduled process.
• Confirming the cadence options.
• Reasoning about scope and outcome surfacing.

Do not use this Reference for:

• Event-based automation — Trigger Model.
• Per-job specifics — corresponding Reference page.
• Step-by-step configuration — Guides.

Public boundary

This page is intentionally public-safe. It does not expose scheduling internals, exact job-runner mechanics, or protected operational identifiers.

Examples

Example 1 — Daily backup runs and operator confirms outcome

The daily backup job runs at 02:00 UTC. Notification Logic delivers a "backup complete" notification. The operator confirms via the schedule status surface (next-run timestamp updated) and the admin Backups module (new snapshot listed).

Example 2 — Weekly report does not arrive

The weekly traffic report fails to deliver on Monday morning. The operator opens the schedule status surface, sees the last-run failed, opens the per-job Reference (Reporting Automations) for the diagnosis context, and reschedules.

Example 3 — Account-tier monthly summary runs across portfolio

The monthly billing-adjacent summary runs at account-tier scope on the 1st of each month. The summary aggregates across every site under the account; the artifact lands in SG-Dashboard Reports for the account owner to review.

Documentation guidance

Use this page as the structural definition for the schedule primitive. Procedural detail belongs in Guides; per-release behavior change belongs in What's New or Changelog. Cross-reference per-job Reference pages for the specifics of any one scheduled process.

Where to find it

In SGEN Admin, navigate to the admin → Configuration → Tools. Scheduled-process outcomes — backup snapshots, generated reports, audit-log entries — surface inside their corresponding modules. The per-job last-run timestamp, next-run timestamp, and current health status appear under the configuration panel for each scheduled process.

Reading order

Open this page after Automation Overview when scoping time-based automation. Pair with Notification Logic for the operator-facing seam and the per-job Reference pages for specifics.

Related reading

• Automation Overview — parent Reference area.
• Trigger Model — event-based counterpart.
• Notification Logic — operator-facing notification layer.
• Backup and Deploy Automation — schedule-driven backup category.
• Reporting Automations — schedule-driven reporting category.

Vocabulary cross-reference

• Scheduled process is a job that runs on a defined cadence.
• Cadence is the time pattern (daily / weekly / monthly / custom).
• Scope is what the job runs against (per-site or account-tier).
• Time-based is the property that distinguishes schedules from triggers (event-based).
• Run is one execution of the scheduled process at the cadence boundary.

Maintenance discipline

When the schedule primitive changes across releases (new cadence option, new scope, new outcome surface), update this Reference and log the change in Changelog. The page stays valuable because the three-part shape (cadence / scope / behavior) stays small.