CapabilityOperations & RuntimeNode.js, read from its artifacts

Job scheduling

Running something later, or on a cadence, without keeping a process alive to do it — a nightly job, a retry in an hour, a report on the first of the month — and knowing afterwards whether it ran.

Showing artifacts, examples and content with confirmed Node.js applicability. View All CAP

Overview

SAP SHIPS
@sap/cds

Schedules a service's events as tasks with srv.schedule(): once, after a delay, or repeatedly on an interval or a cron expression, persisted in the event queue and cancelled with srv.unschedule().

A Node.js coverage assessment has not been written. View all flavors

THE COMMUNITY ADDS

A Node.js coverage assessment has not been written. View all flavors

Artifacts3

3 of 3 artifacts
ArtifactSignals
CDS plugins1
@cap-js-community/event-queueTransactional processing of asynchronous and periodic CAP events
Signals
Functional boundary
Packages1
@sap/cdsCAP Node.js runtime
Signals
none
Services1
SAP Job Scheduling serviceCalls an application endpoint on a schedule and logs each run
Signals
none

Details

What changed — and what it makes stale1
@sap/cds 9.9.0, CAP, Node.js

Before this, the Node.js scheduling API that arrived as alpha in the May 2025 release offered .after() and .every() with a delay or an interval. 9.9.0 added cron expressions to .every(), and srv.schedule.task() and srv.unschedule.task() to create and remove singleton tasks.

Makes stale:

Advice that CAP's own scheduling takes intervals only, and that a cron cadence needs a plugin or an external scheduler.

Coverage
statecore and community, CAP, Node.js, derived
also inBTP/BAIP, ABAP
For your agent
Ref
capability:job-scheduling
JSON
/capabilities/job-scheduling.json
MCP
Connecting an agent