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.
The Job Scheduling service calls an application's endpoint on a schedule or once at a time, keeps a log of every run, and offers a free and a standard plan. The application supplies the endpoint and nothing else.
No community artifact is documented here.
Not covered: Tasks run in the application's own processes from its own database, so a stopped application runs none; the SAP Job Scheduling serviceSAP Job Scheduling serviceCalls an application's endpoint on a schedule or once at a time and keeps the log of every run — cron without a process of your own to keep alive.sap official, btp is the one that calls in from outside. .every() counts from the end of the last successful run, not from a fixed clock.
@cap-js-community/event-queue@cap-js-community/event-queueTransactional processing of asynchronous and periodic events, with instant dispatch over Redis Pub/Sub and load spread across every application instance.community org, cap declares periodic events in its own YAML configuration and spreads them across application instances over RedisRedisAn in-memory data store. For the things here it is the shared cache, the queue or the pub/sub channel that lets several application instances behave as one..
On the ABAP door the system schedules the job itself: abap-platform-application-jobs starts one from a RAP action and shows its status and application log in a Fiori elements app.
Application Jobs: an ABAP report or class registered as a job catalog entry gets a selection screen, a job template refers to the entry, and the job runs in the background from the Application Jobs app or from code through the released API CL_APJ_RT_API.
Not covered: A RAP business object can call the scheduling API only in the additional save phase, so the job name and count are not known during the interaction phase. Code running as an application job cannot be stepped through in the debugger; SAP's sample runs the same class interactively for that.
The one repository here is an SAP sample. It demonstrates the framework and does not count as a provider, so core-only reads what the ABAP platform ships.
No community artifact is documented here.
CAP Java gained the scheduling API in the June 2026 release, which also brought @sap/cds 10: Schedule.create() with .after(), .every() and .cron(), and named tasks that can be cancelled. In both runtimes a named task runs once when the application is scaled horizontally.
Advice that CAP Java has no scheduling of its own.
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.
Advice that CAP's own scheduling takes intervals only, and that a cron cadence needs a plugin or an external scheduler.
capability:job-scheduling