Symptom
The following error message is displayed when attempting to run a data import job in SAP Analytics Cloud:
"Current modelID reached limit or maximum number of active jobs"
Environment
SAP Analytics Cloud Revision 2023 and higher
Reproducing the Issue
- Re-run data separate import jobs into a model until you have reached the maximum number of jobs.
- An error is generated on any new job creation explaining that the maximum number of active jobs has been reached.
Cause
'Active Jobs' are data import jobs that can consist of the following states:
'READY_FOR_DATA', 'READY_FOR_WRITE' or 'READY_FOR_VALIDATON'.
In this case, the maximum number of active jobs for this specific model has been reached.
Rather than fixing an invalid job, a new job has been created, leaving the previous job in an active state.
Resolution
This error is resolvable through the backend only using Postman.
Your SAP Analytics Cloud Administrator should carefully perform the following steps:
SAP Analytics Cloud steps:
- Open the 'App Integration' tab within System -> Administration of SAP Analytics Cloud.
- Make a note of the Client ID, Client Secret and Token URL.
Postman Steps:
- Open a new request in Postman.
- Navigate to the 'Authorization' tab to configure the OAuth Client in Postman.
- Under Auth Type, select 'OAuth 2.0', and input the Client ID, Client Secret, and Token URL.
- Click the 'Get New Access Token' button.
- Next, make a request to <tenant_name>/api/v1/dataimport/jobs to get a list of all the jobs on the tenant, including the 'x-csrf-token' = 'fetch' header.
- In the response, make a note of the header, also called 'x-csrf-token'.
- Find the list of 'Active Jobs', where the job status is 'READY_FOR_DATA', 'READY_FOR_VALIDATON' or 'READY_FOR_WRITE'.
- Make a note of the list of the JobIDs.
- Execute a DELETE call to each jobID using /jobs/<JOB_ID>, to delete the jobs. Include the 'x-csrf-token', which should be set to the CSRF Token, previously obtained from the headers in the request set to /jobs.
- Once the jobs have been cleared, it should now be possible to run data import jobs once more.
See Also
Keywords
Data Import API, Data Import Service, DIS , KBA , LOD-ANA-ML-DI , Data Integration, Data Export API, Data Import API , LOD-ANA-ML , SAC Modelling , Problem