In this blog post, I'm listing some frequently answered questions. I'm skipping those frequently asked questions I wasn't able to answer.
There's also a Frequently Asked Questions page in the Job Scheduling service documentation on SAP Help Portal.
In case of issues, you might have already had a look at the Troublemaking blog post.
General
Q: The creation of a Job Scheduling service instance fails in the SAP BTP cockpit.
A: Try using the Cloud Foundry Command Line Interface (CLI).
Q: In the dashboard, when I open a job and I go to Events in the navigation panel, I can see a column called Actor. Why does it have different values?
A: In case of a manual job creation, it is the user. In case of a programmatic job generation (REST API, multitenant scenarios), it is the ClientID.
Q: I’d like to execute one job per minute.
A: This is currently not supported by the Job Scheduling service.
Q: If executing a job per minute is not supported, is there a workaround?
A: You can schedule multiple jobs for the same endpoint – in a sequence. The schedule would be 1 minute later for each sequent job.
Q: Does the Job Scheduling service store run logs? Are there backups?
A: The execution run logs of the Job Scheduling service are stored during and after execution for a limited time. There are regular backups.
Q: What's the retention period for the backups?
A: 15 days for run logs and DB backups.
Q: How can I set a log level for @Sisn/xssec?
A: To set it, run the following CF CLI command:
cf set-env mutete DEBUG xssec:*
Q: Is there a way to configure a job to run depending on a second job?
A: No, conditional triggers are currently not supported.
Q: Is there an integration of Alert Notification service with the Job Scheduling service?
A: Yes, they are integrated. To learn more about it, read How to integrate Alert Notification Service with Job Scheduler on SAP BTP.
For more information, see SAP Job Scheduling Service Events.
Q: Is the Job Scheduling service available in the SAP BTP, Kyma runtime?
A: Yes, it is. For more information, see Create a Service Instance in the Kyma Dashboard.
Q: My async job or my CF task are stopped (timeout)?
A: The default timeout is 30 minutes. To adjust the timeout setting, go to Configurations in the dashboard.
SAP Cloud Integration
Q: Is it possible to invoke SAP Cloud Integration iFlows exposed as HTTP endpoints from Job Scheduling service?
A:Yes, it is possible. The jobscheduler token would need to be accepted in the HTTP endpoints implementation and on job creation, SAP Cloud Integration would need to ensure that the user is allowed to execute these iFlows.
REST API
Q: How to expose the job creation API to a customer of my multitenant app?
A: It is necessary to have a wrapper API in the provider’s application. Then the customer can authenticate with the provider application and the provider application can forward the job creation requests accordingly.
Giving the customer direct control over the Job Scheduling service REST API is not advised as they could then create a job to any URL with any body, potentially introducing a security risk, e.g. if your app also handles tenant-independent jobs.
Q: I’m using the REST API, in the response of a GET request there is a property “user” which is empty, although there’s a user-token being sent.
A: This property is only relevant in the service plan “lite”, in case of basic authentication.
Multitenancy
Q: For my multitenant app, can I create tenant-aware jobs in the Job Scheduling Service Dashboard?
A: No, this is only possible via REST API, and with tenant-specific JWT token.
Q: Can I try multitenancy with the Job Scheduling service in a Trial account?
A: No, the Job Scheduling service doesn’t support multitenancy in Trial.
Q: With regard to job generation, what is the difference between client-credentials and TokenExchange?
A: Currently, a user doesn’t see any difference. Internally, there might be relevant changes (audit logging, tracking). It is recommended to use TokenExchange anyways.
Q: My multitenant app subscription doesn’t work. What can I do?
A: Try using SaaS REST API to check if the dependency has been properly registered.
On the SAP Help Portal, see Register the Multitenant Application to the SAP SaaS Provisioning Service and Using SAP SaaS Provisioning Service APIs to Manage Multitenant Applications.
Q: I'm having problems with multitenancy.
A: In a few cases, the following setting is required:
When calling the REST API you need to provide the JWT token as a Bearer token and it's important that you also add a header 'x-sap-scheduler-instance-id' containing the Job Scheduling service instance ID from your Job Scheduling service instance.
Q: The JWT token doesn't contain the granted scope, so calling action endpoint fails. It's a multitenant app.
A: In your node app, try to define the grant like this:
properties:
trusted-foreign-xsuaa-instances:
- appId: jobscheduler
clientId: sb-23a365c5-01ec-4d5f-b3b1-d8d00b88e1af!b252|sap-jobscheduler!b4
