cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SAC Import scheduled jobs didn't start at all in a single day schedule

adriano1973
Explorer
0 Likes
480

Hello everyone

in a model A, I set up an import job to retrieve information from a sql query.

I scheduled it, as I have done many times, once a day late night, together with other models B, C, D etc : these other models were scheduled before model A.

Normally it works everything fine, but only for a single day, I have seen from the history logs, that this model A didn't start, but B,C,D started fine.

I expected to see some error in the import job history log or something else, but nothing was written about  model A that day.

The next day, the schedule import job worked fine as usual.

Why could it happen? Is there a way to see some advanced logs to understand why this schedule simply was skipped?

Thank you so much for your help

Adriano

 

Accepted Solutions (0)

Answers (1)

Answers (1)

MKreitlein
Active Contributor
0 Likes

Hello @adriano1973 

A customer of mine found a similar issue right after the QRC2 update.

So, I guess it could happen when SAP updates anything in the backend, or if something takes longer than expected or some minotr update is maybe executed?

We are not fully aware, when SAP does what int he background 😞

BR, Martin

adriano1973
Explorer
0 Likes
Hello Martin, yes it happened on Saturday night when SAP usually makes its updates. Thank you so much for your reply