Hi again,
I have received this answer from MS:
CRM integration jobs can be in two states other than Running and Error: Ready and On Hold with Inactivity Timeout.
If a job is in Ready state, next run will be calculated by "No. of minutes between runs".
If a job is in On Hold with Inactivity Timeout state, next run will be calculated by "Inactivity Timeout Period".
A CRM integration job will be put in On Hold with Inactivity Timeout state if the last job didn't synchronize any records (meaning there were no changes at all).
Final and very important note, a job in On Hold with Inactivity Timeout state will be woken up if there's a change (create new record, modify existing record, delete existing record). For example, CUSTOMER-ACCOUNT job will be woken up if there's any change made to customer records in Business Central.
This would mean that integration jobs are activated from the "On Hold with Inactivity Timeout" state whenever a change is made, so there should never be a long wait between runs at all. I have not yet been able to verify this myself, as we have now equated the timeout period with the time between runs for these jobs. We do not need the runs to be < 5 minutes.
Maybe this information will help.
