Skip to app details
Back to app library
APPNEURAL APP FAMILYAutomation & Integrations

Scheduling Registry

Put recurring work on a schedule

Explore scheduling capabilities and run cron, delayed, and recurring jobs.

01 / OVERVIEW

See where it fits in your day.

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).

A LOOK INSIDEExample layout · sample content
A clear view of scheduled work
MON9
Sample planReport preparation
TUE10
WED11
Sample planContent review reminder
THU12
Sample planRoutine maintenance
FRI13
Illustrative weekly layout
02 / CAPABILITIES

Built around the work you do.

What Scheduling Registry does for you.

01

Scheduling capabilities

Explore reusable scheduling and orchestration capabilities.

02

Cron and delayed jobs

Use the Job Scheduler for cron and delayed jobs.

03

Recurring jobs

Prepare work that runs on a recurring schedule.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Scheduling Registry. What you can do depends on your access in the app.

01

Choose the job pattern

Decide whether the work is cron-based, delayed, or recurring.

02

Review the capability

Find the scheduling or orchestration capability suited to the work.

03

Prepare the schedule

Use the Job Scheduler to define the required timing.

YOUR NEXT MOVE

Make Scheduling Registry part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE44 items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

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).

Time-based and event-driven execution: cron, delayed and recurring jobs, timers, retries, coordination and the runs they produce.

Multi-step automations belong to Workflow; Scheduling owns when work runs, not what its steps do.

Priority
P2
Portfolio
Automation & Integrations
Capability
Automation & Integrations
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:02:59
Semantic inventory

Every number says what it counts

44Catalog itemstrackedEntityCount · catalog-api:live
43ProductionproductionCount · catalog-api:live
1ReferencereferenceCount · catalog-api:live
Production-ready gate

Governance evidence required

6 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
ConfiguredGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

scheduling schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

scheduling.appneurox.com DEPLOYED

scheduling.appneurox.com

Worker
scheduling-catalog
Health
HEALTHY
Last deployment
2026-11-03T00:00:00.000Z
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app