To run a job, the system requires sufficient resources, such as cores and memory. Based on the number of records that a job processes, the system allocates the required resources and completes each process step of the job.
After the job completes each process step, the system changes the status of the job. The change in job status depends on the records that the system processes in each process step.
If the system doesn't have sufficient resources to complete a process step, the system changes the job status from Running to Queued. For example, if you run an ingress job with 10,000 records, the job requires sufficient resources in the system to complete each process step. After the transform step, if the system doesn't have sufficient resources to complete the load step, the system queues the job.
Note: The system doesn't queue egress jobs and the extract step of ingress jobs.
When a process hierarchy job is running for a particular hierarchy, no other job can run simultaneously for the same hierarchy. Instead, the subsequent jobs are queued and remain in a queued state until the previous job is complete.