MyAlgoGuru Help
Education Glossary Open the app
Help/Reference/Automation

Scheduler

Time-based jobs — define a schedule, enable or pause it, trigger it on demand, and keep a full run history.

Where you will find this

Scheduler.

Purpose

The scheduler runs actions on a cadence (cron, interval or one-off). Each run is recorded and emits a domain event, so downstream automation can react and you always have an audit of what ran and when.

The Scheduler module provides a central business capability for planning, managing and executing time-based business activities across the platform.

It enables authorised users and business modules to define recurring or one-time schedules that trigger business processes at specified times or intervals.

The Scheduler serves as the platform-wide time orchestration capability.

Objectives

The module will:

  • Schedule business activities.
  • Execute scheduled business activities.
  • Support recurring schedules.
  • Support one-time schedules.
  • Maintain schedule history.
  • Monitor schedule execution.
  • Enable time-driven business automation.

Functional Scope

The module includes:

  1. Schedule Definition
  2. Schedule Configuration
  3. Schedule Activation
  4. Schedule Execution
  5. Schedule Monitoring
  6. Schedule History
  7. Schedule Search
  8. Schedule Audit

Schedule Model

A schedule represents a planned execution of a business activity based on time.

Each schedule will define:

  • Business Activity
  • Execution Timing
  • Execution Frequency
  • Schedule Status

Schedules remains independent of implementation technology.

Schedule Definition

The platform will support creation of business schedules.

Typical scheduled activities include:

  • Strategy Execution
  • Market Scans
  • Portfolio Rebalancing
  • Historical Data Refresh
  • Report Generation
  • Data Import
  • Data Export
  • Health Checks
  • End-of-Day Processing
  • Start-of-Day Processing

The design will support additional scheduled activities.

Schedule Configuration

Each schedule will maintain its execution configuration.

Typical configuration includes:

  • Schedule Name
  • Business Activity
  • Execution Frequency
  • Start Date
  • End Date
  • Time Zone
  • Execution Window
  • Schedule Status

Configuration remains extensible.

Schedule Types

The platform will support multiple schedule types.

Typical schedule types include:

  • One-Time Schedule
  • Daily Schedule
  • Weekly Schedule
  • Monthly Schedule
  • Interval-Based Schedule
  • Trading-Day Schedule
  • Market Session Schedule
  • Event-Triggered Schedule

The design will support additional schedule types.

Schedule Execution

The platform will execute eligible business activities according to their schedule.

Execution includes:

  • Schedule Validation
  • Activity Initiation
  • Execution Status Recording
  • Completion Recording

The Scheduler will initiate execution but does not perform the underlying business activity.

Schedule Monitoring

The platform will monitor scheduled activities.

Monitoring may include:

  • Upcoming Executions
  • Running Activities
  • Completed Activities
  • Failed Activities
  • Missed Executions
  • Execution Duration

Monitoring will support operational visibility.

Schedule History

Historical schedule activities is preserved.

History includes:

  • Schedule Definition
  • Execution Timestamp
  • Execution Status
  • Completion Status
  • Failure Information

Historical records remains immutable.

Authorised users is able to search schedules.

Typical search criteria include:

  • Schedule Name
  • Business Activity
  • Schedule Type
  • Status
  • Date Range
  • Execution Outcome

Search capabilities will support operational management.

Business Rules

  • Every schedule will have a unique identifier.
  • Every schedule will reference one business activity.
  • Only active schedules will execute.
  • Schedule execution is recorded.
  • Failed executions is recorded.
  • Historical schedule records will never be deleted.
  • Schedule execution does not modify schedule definitions.
  • Business activities remains responsible for their own processing.

Audit Requirements

The platform will maintain an audit trail for scheduling activities.

Audit events includes:

  • Schedule Creation
  • Schedule Modification
  • Schedule Activation
  • Schedule Deactivation
  • Schedule Execution
  • Execution Failure
  • Schedule Archive

Audit records remains immutable.

Out of Scope

The following are outside the scope of this module:

  • Strategy Logic
  • Order Execution
  • Market Data Processing
  • Portfolio Valuation
  • Notification Delivery
  • Event Publication

These responsibilities belong to their respective business modules.

Create a scheduled job

  1. Create a job: name it, pick the schedule type (cron / interval / once) and expression.
  2. Choose the action it performs.
  3. Enable it — or trigger it manually to test. Each run is recorded with its status.
  4. Pause or disable the job at any time without deleting its history.