Symptom
- Delay in notification of refresh failures in Models
- Even schedule failed several times, but only one failed could be recorded in Activities log and only one notification send to users
Environment
- SAP Analytics Cloud 2023.23.2
Reproducing the Issue
- Create a import model.
- Create a import job for the model.
- In the Schedule Settings, set with Repeating, and Recurrence frequently, for example every 20 minutes.
- Save.
Cause
Job takes a very long time to finish and it's taking longer than the next occurrence.
Resolution
When job takes a very long time to finish and it's taking longer than the next occurrence, system will not send failure as the next job will not run if the previous job is in progress.
Will only send out a failure if the job actually runs.
However, to make sure that you do not see failures and job trying to run while the previous job is still running.
Please increase the time between each schedule run so that the next job does not try to run while your previous job is still running.
Increasing the time between job will solve your delay notification issue.
Please increase the time between each run to ensure that you schedule the next run only after the previous job finishes.
Then you will not see this issue.
Keywords
failed, multi, error, email , KBA , LOD-ANA-AQU , Import Data Connections (Acquiring Data) , Problem