TechPrufer
Get started
Temporal
Temporal logoTemporal · Feature trail

Workflow Scheduling

5 posts · Dec 2022 – Aug 2025

What this trail covers

Temporal Schedules provide a robust and observable alternative to traditional scheduling systems like Cron, systemd timers, and Celery. This feature allows for the execution of Temporal Workflows at specific times or intervals, offering enhanced control over task operations such as starting, pausing, resuming, backfilling, deleting, describing, listing, triggering, and updating scheduled workflow executions. Schedules support features like limiting runs, configuring overlap policies, and pausing on failure. This post details the migration of existing scheduling systems to Temporal Schedules, providing examples for Kubernetes CronJobs, systemd Timers, Quartz, and Celery. It emphasizes wrapping existing scripts in Activities within single-activity Workflows or implementing jobs as full Temporal Workflows to leverage Temporal's capabilities. The post also highlights the command-line and SDK-based creation of schedules, including calendar and interval-based scheduling, and overlap policies.

All Temporal trails
  1. Enabling platform engineering with Temporal: 5 practical use casesThis post details five practical use cases for Temporal in platform engineering: Incident response and runbook automation, certificate rotation, infrastructure management, CI/CD pipeline orchestration, and Internal Developer Platform (IDP) automation. It highlights how Temporal Workflows can encode complex operational logic as code, providing resilience, state persistence, human-in-the-loop capabilities, and auditability. Specific examples include Datadog's use of Temporal for migrations, Temporal Cloud's support for certificate rotation, and Netflix's re-platforming of Spinnaker. The post emphasizes Temporal's ability to manage long-running, fault-tolerant workflows for resource lifecycle management, CI/CD pipelines with dynamic rollbacks, and IDP automation by abstracting complex tasks behind simple workflow triggers.
  2. Trading Airflow + EMR for Temporal + Bauplan: The Mediaset taleThis post details Mediaset's migration from a legacy Airflow and AWS EMR/Glue/Athena/Redshift stack to Temporal and Bauplan. It highlights the benefits of using Temporal for orchestration, specifically its durable, replayable workflows with automatic retries and built-in scheduling, which replaced Airflow and improved data freshness from 1 hour to 5 minutes. The post contrasts Temporal's code-centric approach with Airflow's YAML-based debugging and emphasizes Temporal's reliability and ease of use for complex flows.
  3. Spooky Stories: ​​Taming deployment complexity with TemporalThis post details how Temporal Workflows can be used to manage complex deployment processes, including multi-repository builds, blue-green deployments, and manual approval steps. It illustrates how Temporal's durable execution model simplifies these scenarios by providing built-in retries, state management, and fault tolerance, reducing the need for custom "systems" to handle these complexities. The post uses examples from GitHub Actions and discusses how Temporal can abstract away much of the underlying infrastructure and coordination.
  4. Workflow History Export Insights on Temporal CloudThis post introduces the Workflow History Export feature on Temporal Cloud, enabling users to export closed workflow histories to AWS S3 for analysis. It details the process of transforming Protocol Buffer data to Parquet for easier analysis, setting up ETL pipelines, and provides sample SQL queries for analyzing workflow and activity execution frequency and duration. It also discusses building dashboards for visualization and outlines current limitations of the export feature.
  5. Convert Your Job Scheduler to Temporal SchedulesThis post details the migration of existing job scheduling systems (Kubernetes CronJobs, systemd Timers, Quartz, Celery) to Temporal Schedules. It provides concrete examples of how to translate schedules from these systems into Temporal's `schedule create` CLI commands and SDK configurations, including calendar-based and interval-based scheduling, overlap policies, and input parameters. The post also outlines a general migration strategy involving understanding existing schedules, wrapping non-Temporal scripts in Activities within single-activity Workflows, or implementing jobs as full Temporal Workflows, and deploying these workflows with appropriate task queues, Workflow IDs, and Workflow Types. It emphasizes the benefits of Temporal Schedules, such as enhanced control, observability, and the ability to manage schedules like applications with a full software development lifecycle.
  7. Cron to Schedule ConversionThis post details the process of converting traditional cron jobs to Temporal Schedules, highlighting the benefits of enhanced workflow control, visibility, flexible scheduling, and elimination of external dependencies. It provides code examples in TypeScript, Go, Java, .NET, and Python demonstrating how to create Temporal Schedules using SDKs and the CLI.
  8. Temporal Schedules: More Reliable & Scalable than Cron JobsThis post announces the general availability of Temporal Schedules, a new feature designed to replace traditional Cron jobs. It highlights the advantages of Temporal Schedules over Cron, such as enhanced workflow control and observability, flexible scheduling with overlap policies, and the elimination of external dependencies. The post includes practical examples of creating and viewing schedules using `tctl` and the Temporal Web UI, and lists the SDKs that now support this feature.
  9. Sync GitHub Repos to Notion with Temporal SchedulesThis post demonstrates the use of Temporal Schedules to reliably execute a daily synchronization task between GitHub repositories and a Notion database. It contrasts this with the unreliability of GitHub Actions cron jobs and highlights how Temporal's durable functions ensure retries and continued execution even in case of failures. The implementation involves a TypeScript function that fetches data from the GitHub API and updates a Notion database via its client library, scheduled to run daily using Temporal Schedules.
  10. Temporal v1.20: Enhanced Dev Environments & SchedulingIntroduced the General Availability of Scheduled Workflows in Temporal v1.20, providing a more robust and controllable alternative to Temporal Cron Jobs. Key enhancements include independent Schedule entities, editability of Schedule specifications, pause/running states, run limits, backfilling capabilities, overlap policies, and pause-on-failure configurations. Added support for Schedules in the CLI, Go SDK, TypeScript SDK, and Python SDK. Also, simplified local development environments by packaging Temporalite as the Temporal CLI, which replaces containerized setups and includes Advanced Visibility.
  11. How to build scheduled WorkflowsThis post details the "Why?" and "How?" of Temporal's new Scheduler feature, which replaces a previous simple schedule feature with improved capabilities like stopping/pausing schedules independently of workflows, updating configurations, supporting overlapping runs, and providing better visibility. The decision was made to build the Scheduler as a Workflow directly within the Temporal Server for code reuse and flexibility. Key engineering challenges addressed include running scheduler Workflows in user Namespaces while using system Namespace task queues, requiring additional SDK workers per Namespace. To "hide" these internal Workflows from user queries, a search attribute was introduced to create "Namespace divisions." Interaction with the scheduler uses gRPC APIs, with signals for state changes and a novel approach involving frontend service checks and signals to accurately describe running Workflows due to the lack of direct child workflow completion notifications.