plugins/sap-btp-job-scheduling/skills/sap-btp-job-scheduling/SKILL.md
This skill provides comprehensive guidance for SAP BTP Job Scheduling Service development, configuration, and operations. It should be used when creating, managing, or troubleshooting scheduled jobs on SAP Business Technology Platform. The skill covers service setup, REST API usage, schedule types and formats, OAuth 2.0 authentication, multitenancy, Cloud Foundry tasks, Kyma runtime integration, and monitoring with SAP Cloud ALM and Alert Notification Service. Keywords: SAP BTP, Job Scheduling, jobscheduler, cron, schedule, recurring jobs, one-time jobs, Cloud Foundry tasks, CF tasks, Kyma, OAuth 2.0, XSUAA, @sap/jobs-client, REST API, asynchronous jobs, action endpoint, run logs, SAP Cloud ALM, Alert Notification Service, multitenancy, tenant-aware, BC-CP-CF-JBS
npx skillsauth add secondsky/sap-skills sap-btp-job-schedulingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
SAP Job Scheduling Service is a runtime-agnostic platform service for defining and managing one-time and recurring jobs or Cloud Foundry tasks on SAP BTP. It operates across multiple hyperscalers (AWS, Azure, GCP) without requiring application modifications.
Documentation Source: https://help.sap.com/docs/job-scheduling
Last Verified: 2025-11-27
Use this skill when:
Setup & Configuration
├─ Initial setup prerequisites → references/setup-guide.md
├─ Create service instance
│ ├─ BTP Cockpit → references/setup-guide.md#cockpit
│ ├─ CF CLI → references/setup-guide.md#cf-cli
│ └─ Kyma Dashboard → references/setup-guide.md#kyma
└─ Configure XSUAA scopes → references/security.md
Job Management
├─ Create jobs → references/rest-api.md#create-job
├─ Configure schedules → references/rest-api.md#schedules
├─ Run logs & monitoring → references/rest-api.md#run-logs
└─ Dashboard operations → references/operations.md#dashboard
Schedule Configuration
├─ One-time vs recurring → references/concepts.md#schedule-types
├─ Cron format → references/concepts.md#cron-format
├─ Date/time formats → references/concepts.md#date-formats
└─ Human-readable → references/concepts.md#human-readable
Asynchronous Execution
├─ Async mode flow → references/concepts.md#async-mode
├─ Callback implementation → references/rest-api.md#update-run-log
└─ CF tasks → references/concepts.md#cf-tasks
Security & Authentication
├─ OAuth 2.0 setup → references/security.md#oauth
├─ XSUAA configuration → references/security.md#xsuaa
└─ Credential rotation → references/security.md#rotation
Integrations
├─ SAP Cloud ALM → references/integrations.md#cloud-alm
└─ Alert Notification → references/integrations.md#alert-notification
Troubleshooting
├─ Common errors → references/troubleshooting.md#errors
├─ FAQ → references/troubleshooting.md#faq
└─ Support: BC-CP-CF-JBS
Version History & Updates
└─ What's New (2021-2025) → references/changelog.md
A collection of schedules with an action endpoint. Jobs invoke a configured URL at specified times synchronously (short operations) or asynchronously (long processes).
A one-time or recurring entity within a job. Supports multiple formats (cron, date/time, human-readable) and has three lifecycle states: SCHEDULED → RUNNING → COMPLETED.
An HTTP/REST endpoint exposed by your application that the service invokes when schedules trigger. Must be OAuth 2.0 protected in production.
An app or script that runs independently in its own container. Always executes asynchronously with configurable memory allocation.
| Constraint | Value | |------------|-------| | Minimum schedule interval | 5 minutes | | Synchronous request timeout | 15 seconds | | Asynchronous timeout (default) | 30 minutes (configurable up to 7 days) | | POST request body limit | 100 KB | | Run log retention | 15 days | | Service SLA | ~20 minutes from scheduled time |
| Format | Example | Use Case |
|--------|---------|----------|
| Cron | * * * * 10:12 0,30 0 | Every 30 min between 10:00-12:00 |
| Date/Time | 2025-10-20T04:30:00Z | ISO-8601 one-time execution |
| Human-readable | tomorrow at 4pm | Natural language scheduling |
| repeatInterval | 2 hours, 5 minutes | Recurring at fixed intervals |
| repeatAt | 4.40pm, 18:40 | Daily at specific time |
Year Month Day DayOfWeek Hour Minute Second
* * * * * * *
| Field | Values | Special | |-------|--------|---------| | Year | 4-digit (2025) | * = any | | Month | 1-12 | */a = every a-th | | Day | -31 to 31 | negative = from end | | DayOfWeek | mon, tue, wed... | a.y = a-th occurrence | | Hour | 0-23 | a:b = range | | Minute | 0-59 | a:b/c = step in range | | Second | 0-59 | a,b,c = multiple values |
| Phase | States | Description | |-------|--------|-------------| | SCHEDULED | SCHEDULED | Queued for future run | | RUNNING | TRIGGERED, ACK_RECVD, ACK_NOT_RECVD | Executing | | COMPLETED | SUCCESS, ERROR, REQUEST_ERROR, UNKNOWN | Finished |
| Method | Endpoint | Purpose |
|--------|----------|---------|
| POST | /scheduler/jobs | Create job |
| GET | /scheduler/jobs | List all jobs |
| GET | /scheduler/jobs/{id} | Get job details |
| PUT | /scheduler/jobs/{id} | Update job |
| DELETE | /scheduler/jobs/{id} | Delete job |
Avoid Peak Times:
Use Irregular Times:
01:12:17 instead of 01:00:0001:38:37 instead of 01:30:00x-sap-job-id, x-sap-job-schedule-id, x-sap-job-run-id, x-sap-scheduler-host"time": "now" for immediate execution# Get access token
curl -X POST "<uaa_url>/oauth/token" \
-H "Authorization: Basic $(echo -n '<clientid>:<clientsecret>' | base64)" \
-d "grant_type=client_credentials"
# Use token in API calls
curl -X GET "https://jobscheduler-rest.<landscape>/scheduler/jobs" \
-H "Authorization: Bearer <access_token>" \
-H "Content-Type: application/json"
{
"xsappname": "<app-name>",
"scopes": [{
"name": "$XSAPPNAME.JOBSCHEDULER",
"description": "Job Scheduler Scope",
"grant-as-authority-to-apps": ["$XSSERVICENAME(<jobscheduler-instance>)"]
}]
}
POST /scheduler/jobs
{
"name": "myJob",
"description": "Process daily reports",
"action": "https://myapp.cfapps.eu10.hana.ondemand.com/api/process",
"active": true,
"httpMethod": "POST",
"schedules": [{
"active": true,
"description": "Daily at 6 AM",
"repeatAt": "6.00am",
"startTime": {"date": "2025-01-01", "format": "YYYY-MM-DD"}
}]
}
Requirements: Node.js 14.x or later
npm install @sap/[email protected]
const JobSchedulerClient = require('@sap/jobs-client');
const scheduler = new JobSchedulerClient.Scheduler();
// Create job
scheduler.createJob({ url: vcapServices.jobscheduler[0].credentials.url }, {
name: 'myJob',
action: 'https://myapp.../process',
active: true,
httpMethod: 'GET',
schedules: [{ cron: '* * * * 0 0 0', active: true }]
}, (err, result) => { /* handle */ });
| Limit Type | Response Code | Header |
|------------|---------------|--------|
| Client limit exceeded | 429 | retry-after (seconds) |
| Absolute limit exceeded | 503 | throttling (milliseconds) |
Limits stack - both can apply simultaneously.
| Outage Duration | Behavior | |-----------------|----------| | < 20 minutes | All missed executions run immediately | | >= 20 minutes | Only last missed execution runs |
Setup:
grant-as-authority-to-appsScheduling:
Async Jobs:
Multitenancy:
tenantId filter with SaaS tenant tokens (returns 400)Source: SAP BTP Job Scheduling Service Documentation
To Update This Skill:
Quarterly Review Recommended: Check for updates every 3 months
Next Review: 2026-02-27
License: GPL-3.0 Maintainer: Eduard Jiglau | [email protected] | sap-ai-skills.com | https://github.com/secondsky/sap-skills
tools
Use when automating SAP BW query inspection, InfoProvider metadata reads (characteristics, key figures), metadata-verified specification review, unsaved draft preparation, or human-confirmed query draft population through Eclipse or HANA Studio with BW Modeling Tools.
tools
Use when an agent must inspect or operate an authenticated SAP web UI through an in-app Browser, Microsoft Edge CDP, or an existing Playwright client, especially when SAP SSO reuse, isolated Edge profiles, deterministic target selection, screenshots, or browser bootstrap recovery is required.
tools
Evidence-based assessment of whether an SAP API/interface usage scenario aligns with the SAP API Policy (v.4.2026a). Use whenever someone asks whether a way of calling SAP is allowed/compliant — e.g. Published API vs internal/private/"confidential" API status, "Documented Use", whether a third-party tool / iPaaS / middleware / RPA bot / AI agent / MCP server may call SAP APIs, agentic or generative-AI access to SAP, bulk data extraction or replication into a lake/warehouse, custom Z/Y OData or RFC/BAPI wrappers and Clean Core, ADT/developer-tooling boundaries, ODP-RFC and other "not permitted" interfaces, partner Integration Certification, or RISE integration remediation. Trigger even when the policy is not named, e.g. "are we allowed to…", "is it compliant to…", "can we connect X to SAP…", "will this break under the new API policy". Produces a sourced technical assessment with a confidence level — explicitly NOT legal advice and NOT a final SAP compliance decision.
development
SAP-RPT-1-OSS local tabular prediction workflows for FI/CO prototype datasets. Use when preparing SAP finance CSV exports for classification or regression experiments with source-verified setup, leakage checks, and governance review.