I have a schema which takes ~ 13 hours to load doing a full load.
Last night it finished ~ 1:30 a.m. which is 1/2 hour *past* the scheduled incremental build time.
I would have expected the scheduler to queue the incremental build and run it directly after the full load, but instead it seems to have shrugged its virtual shoulders, said "it's already going," and didn't attempt to run the load at all.
1) Expected behavior? 2) Can I force the incremental to queue if a load is underway during the scheduled kickoff time?
Unfortunately Incorta doesn't maintain such behavior , For any schema schedules that get overlap the second load will get skipped.
You can use Incorta APIs in the meantime to implement this behavior with a custom script.