FAQs
Why does an import schedule sometimes take longer?
We have a process which runs every hour. On that hour, it picks up the total number of import wizard jobs that should be started and runs them in parallel. It prioritizes jobs, putting jobs that recently ran last. Typically, for most customers, the imports all run, and the schedule will start again in the next hour.
However, if you see delays, it is most likely due to Salesforce scheduled job limits. Salesforce has a limit of 100 scheduled jobs. This limit is org-wide, so if you have other scheduled jobs, the number of slots we have to work with would be less. To help with this, we impose a limit of 80 records, although this can be changed. For example, if you already had 50 jobs scheduled and 80 import wizards were scheduled, we would attempt to run 30 jobs.
We also have some additional checks to ensure we operate within Salesforce’s resource constraints. First, we check to see if the Last Run for an import job was completed. We then check to see if the last run date was over 12 hours ago, as it could be stale. After completing these checks, we will loop through and start the individual import jobs, checking that Salesforce still has scheduled job slots we can use. Of course, this could mean we cannot start all 30 jobs. Once this process is completed, we begin the process again in the next hour.
However, if you see delays, it is most likely due to Salesforce scheduled job limits. Salesforce has a limit of 100 scheduled jobs. This limit is org-wide, so if you have other scheduled jobs, the number of slots we have to work with would be less. To help with this, we impose a limit of 80 records, although this can be changed. For example, if you already had 50 jobs scheduled and 80 import wizards were scheduled, we would attempt to run 30 jobs.
We also have some additional checks to ensure we operate within Salesforce’s resource constraints. First, we check to see if the Last Run for an import job was completed. We then check to see if the last run date was over 12 hours ago, as it could be stale. After completing these checks, we will loop through and start the individual import jobs, checking that Salesforce still has scheduled job slots we can use. Of course, this could mean we cannot start all 30 jobs. Once this process is completed, we begin the process again in the next hour.
