Scheduler With Configurable Execution Intervals And Cron Based Scheduling

via “cron-based and delayed task scheduling”

Background jobs framework for TypeScript.

Unique: Implements timezone-aware cron scheduling with automatic DST handling via the delayedRunSystem, storing scheduled runs in the database rather than in-memory, ensuring schedules survive process restarts and are queryable for debugging.

vs others: Provides database-backed scheduling with timezone awareness, making it more reliable than node-cron for production use, while being simpler to configure than Temporal's calendar-based scheduling.

via “scheduler workflow for recurring and delayed execution”

Durable execution for distributed workflows.

Unique: Scheduler Workflow is a built-in system workflow that uses the same durable execution model as user workflows, ensuring that scheduled executions are not lost even if the scheduler crashes. Schedules are stored in the workflow history, providing an audit trail of all scheduled executions.

vs others: More reliable than external cron jobs (cron, Quartz) because scheduled executions are persisted in the workflow history and automatically retried on failure, whereas cron jobs can be lost if the cron daemon crashes.

via “scheduled workflow execution with cron-based triggers”

Build, deploy, and orchestrate AI agents. Sim is the central intelligence layer for your AI workforce.

Unique: Provides cron-based scheduling with timezone awareness, automatic retry with exponential backoff, and execution history tracking — enabling reliable recurring workflows without external scheduling services

vs others: More integrated than external schedulers (cron, systemd) because scheduling is defined in the UI; more reliable than simple setInterval because it persists scheduled jobs and survives process restarts

via “flow trigger scheduling with cron expressions and interval-based execution”

Open-source no-code automation tool.

Unique: Implements cron-based scheduling with timezone awareness and execution window configuration, allowing users to define complex schedules without writing code — a feature typically found in enterprise job schedulers

vs others: More flexible than simple interval-based scheduling because cron expressions support complex patterns (e.g., 'every weekday at 9 AM'), but requires understanding cron syntax which has a learning curve

via “cron-based job scheduling with timezone and concurrency control”

Developer platform for internal tools.

Unique: Integrates scheduling directly into the platform with concurrency limits and timezone awareness, avoiding separate cron infrastructure; schedule definitions are version-controlled as code

vs others: Simpler than Airflow for basic scheduling (no DAG compilation), and more reliable than system cron because execution is tracked in the database with retry logic

via “scheduler with cron-based and interval-based workflow triggers”

Unified orchestration with declarative YAML.

Unique: Implements a dedicated Scheduler service that evaluates cron expressions and queues workflow executions with built-in deduplication for clustered deployments, eliminating the need for external cron jobs or scheduling infrastructure

vs others: Simpler than managing system cron jobs and more reliable than Airflow's single-scheduler model because it supports distributed scheduler instances with automatic deduplication

via “scheduled workflow execution via cron expressions”

A durable workflow execution engine for Elixir

Unique: Integrates scheduling directly into the workflow engine via PostgreSQL, eliminating the need for external cron infrastructure or scheduler services. Scheduled workflows are first-class workflow instances with full durability and observability, enabling unified management of all workflows (ad-hoc and scheduled) via the same API.

vs others: Simpler than managing external cron jobs and more integrated than Oban's job scheduling (which treats schedules as separate from workflow orchestration). Schedules are queryable and manageable via API.

via “scheduler with configurable execution intervals and cron-based scheduling”

Placeholder for the old Airflow package

Unique: Implements scheduler as a long-running process with configurable heartbeat loop that parses DAGs, creates task instances, and monitors progress. Supports cron-based scheduling with 1-minute minimum granularity. Single-threaded design in early versions limits scalability but simplifies reasoning about scheduling order.

vs others: More flexible than cron for complex workflows; integrated task dependency management is better than separate cron jobs. Single-threaded scheduler is simpler than distributed schedulers (Kubernetes, Nomad) but less scalable.

via “scheduled workflow execution with cron and interval-based triggers”

Workflow orchestration and management.

Unique: Implements schedule evaluation as a centralized background service that creates flow runs at scheduled times, enabling deterministic and idempotent scheduling without external cron infrastructure; schedules are stored as deployment metadata and can be modified without redeploying code

vs others: Simpler than Airflow's DAG scheduling because schedules are declarative and not embedded in code; more reliable than external cron jobs because schedule state is managed by Prefect and can be queried and modified via API

via “scheduled task execution with cron-based triggers”

[Documentation](https://docs.airplane.dev/?utm_source=awesome-ai-agents)

Unique: Integrates cron-based scheduling directly into the workflow platform with timezone awareness and execution history tracking, eliminating the need for separate cron job management or external schedulers

vs others: More reliable than cron jobs on individual servers because execution is centrally managed with audit logs and failure notifications, versus cron's silent failures and lack of visibility

via “workflow scheduling and recurring execution”

|[URL](https://www.anygen.io/)|Free Trial/Paid|

Unique: Provides both cron-expression and calendar-based scheduling interfaces, with timezone-aware execution and visibility into scheduled vs. actual execution — users can choose between technical (cron) and user-friendly (calendar) scheduling methods

vs others: More flexible than simple time-based triggers because it supports complex recurrence patterns and provides visibility into scheduled execution history, enabling debugging of missed or delayed runs

via “scheduled workflow execution”

via “workflow scheduling with cron-like time-based triggers”

Unique: Scheduling is integrated into the workflow builder rather than requiring separate scheduler configuration; likely uses a visual schedule picker for non-technical users rather than requiring cron syntax knowledge

vs others: More accessible than cron jobs or AWS Lambda scheduled events for non-technical users, but less flexible than dedicated job schedulers (Quartz, APScheduler) for complex scheduling patterns

via “scheduled workflow execution with cron-based triggers”

Unique: Combines cron-based scheduling with visual UI for non-technical users, abstracting away cron syntax while maintaining flexibility for power users

vs others: More accessible than raw cron jobs or cloud scheduler APIs, with built-in timezone support and execution history, though less flexible than custom scheduling logic

via “scheduled workflow execution with cron-based timing”

Unique: Provides simplified scheduling UI for non-technical users (daily, weekly, monthly) alongside cron expression support for advanced users — single interface serves both audiences

vs others: Easier to use than managing cron jobs directly; however, less flexible than dedicated job scheduling systems (Apache Airflow, Kubernetes CronJobs) for complex scheduling patterns

via “scheduled job execution with cron syntax”

via “scheduled web task execution with cron-like triggers”

Unique: Provides cron-like scheduling directly in the UI without requiring users to understand cron syntax, with visual schedule builders and timezone support integrated into the workflow designer

vs others: More user-friendly than setting up cron jobs manually or using Zapier's schedule triggers because scheduling is built into the workflow interface; less flexible than custom cron because it likely doesn't support complex scheduling patterns

via “scheduled workflow execution with cron-like triggers”

via “scheduled workflow execution”

via “workflow-scheduling-and-triggers”