Migration App now empowers users with an upgraded capability to automatically queue migration jobs when the limit for concurrent jobs is reached. Previously, users could not create additional migration jobs once the maximum limit of 4 concurrent jobs (default) was reached, leading to potential workflow disruptions.
With this feature, migration jobs exceeding the limit are seamlessly added to a queue, ensuring they are processed automatically as resources become available.
- Currently, the default limit for the concurrent migration jobs is set to 4 jobs.
- The feature is available on request. Please contact Support to get this feature enabled.
Once a job finishes, whether it is successful, failed, or stopped, the system automatically selects and initiates the next job in the queue.
Currently, jobs are prioritized in the queue on a first-come, first-served basis. For instance, if there are four jobs with an in-progress status and the customer creates three more jobs (J1, J2, and J3) at 13:00, 14:00, and 14:05 Hrs on the same day, respectively, all of these new jobs will initially remain in the queued status.
As soon as any of the in-progress jobs is completed or fails, J1 will be picked for execution, followed by J2 and then J3, based on their creation time.
Users can hover over the newly added jobs in the queued status to learn more about the mechanism involved.