Scheduling capabilities
Explore reusable scheduling and orchestration capabilities.
Put recurring work on a schedule
Explore scheduling capabilities and run cron, delayed, and recurring jobs.
A searchable catalog of 44 scheduling and orchestration capabilities across 8 domains: cron jobs, delayed queues, workflow timers, distributed coordination, retry policy, calendars, resource scheduling and monitoring. The home page is the Job Scheduler, which runs scheduled jobs on Cloudflare Cron Triggers, Queues and Durable Objects; the capability catalog is at /catalog. Per domain: scheduling.<domain> holds one domain's scheduled jobs (79 domains).
What Scheduling Registry does for you.
Explore reusable scheduling and orchestration capabilities.
Use the Job Scheduler for cron and delayed jobs.
Prepare work that runs on a recurring schedule.
A suggested path for Scheduling Registry. What you can do depends on your access in the app.
Decide whether the work is cron-based, delayed, or recurring.
Find the scheduling or orchestration capability suited to the work.
Use the Job Scheduler to define the required timing.
Live host, inventory, governance, health checks, verification, dependencies and history.
A searchable catalog of 44 scheduling and orchestration capabilities across 8 domains: cron jobs, delayed queues, workflow timers, distributed coordination, retry policy, calendars, resource scheduling and monitoring. The home page is the Job Scheduler, which runs scheduled jobs on Cloudflare Cron Triggers, Queues and Durable Objects; the capability catalog is at /catalog. Per domain: scheduling.<domain> holds one domain's scheduled jobs (79 domains).
Multi-step automations belong to Workflow; Scheduling owns when work runs, not what its steps do.
6 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
schedulings.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.