GitHub Workflow Dispatcher

The Problem GitHub Actions scheduled workflows rely on shared platform timers with no execution guarantees. Workflows frequently experience delays ranging from fifteen minutes to several hours during peak platform traffic, or fail to trigger entirely without logging an error or alerting maintainers. In organizations managing multi-repository architectures, teams also lack a single control plane to discover which repositories contain manually dispatchable workflows, inspect required input schemas, trigger jobs on demand, and audit who initiated each run. The Solution & Target Users GitHub Workflow Dispatcher is a centralized workflow orchestration and scheduling platform designed for DevOps teams, platform engineers, and developers. It replaces GitHub's unreliable cron triggers with an independent, deterministic scheduler while providing a unified dashboard for organization-wide workflow management. Users interact with the system through a responsive web interface or a REST API. Once connected through an installed GitHub App, the system automatically catalogs all organization repositories, parses workflow definitions to identify manual triggers, and displays dispatchable actions. Users can trigger workflows on demand with validated custom parameters or configure recurring precision schedules in UTC. Why It Is Unique and Creative Existing tools either rely on GitHub's native cron or require heavyweight external orchestrators that introduce substantial operational overhead. GitHub Workflow Dispatcher provides a lightweight, focused alternative: 1. Independent UTC Scheduling with Jitter Control: An internal scheduling engine triggers workflows precisely when scheduled, completely decoupled from GitHub's internal runner queue delays. Configurable execution jitter distributes triggers across small randomized windows to prevent API rate-limit spikes during bulk runs; 2. Automated Trigger Discovery: The system automatically analyzes remote workflow configurations to detect dispatchable workflows, tracking file hashes to ensure efficient synchronization without redundant API calls; 3. Resilient Token-Bucket Rate Limiting: An asynchronous token-bucket rate limiter enforces outbound request thresholds and manages backoff retries, preventing secondary GitHub API rate limits; 4. End-to-End Audit Trail: Every manual or scheduled dispatch records input parameters, execution source, and the resulting GitHub Actions run URL in a local database, providing full traceability across an entire GitHub organization.