---
schema_version: "1"
id: 590910154de6c3c5a0d62d91370e4d71f76b4fa1328a8d649a15c5820c311f16
title: Does a Retrieve Job Have a Status of Pending?
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_deploy_concurrent_retrieve.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_concurrent_retrieve.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 6f63b7a03298995efd2443a6a19e79f96cba818c6db184a8c1f2a604e5fe62f3
description: If you initiate several concurrent retrieve operations for a single org, Metadata API automatically puts some of those jobs in a queue, if that becomes necessary for service protection. If a retrieve job has a status of Pending, it’s in the queue. When one of the active retrieve jobs completes, Metadata API takes a pending job from the queue and activates it. If a retrieve job has a status of InProgress, it’s active. The process repeats until the job queue is cleared.
---
# Does a Retrieve Job Have a Status of Pending?

If you initiate several concurrent retrieve operations for a single org, Metadata API automatically puts some of those jobs in a queue, if that becomes necessary for service protection. If a retrieve job has a status of Pending, it’s in the queue. When one of the active retrieve jobs completes, Metadata API takes a pending job from the queue and activates it. If a retrieve job has a status of InProgress, it’s active. The process repeats until the job queue is cleared.

For more information, see "Metadata Limits" in the Salesforce Developer Limits and Allocations Quick Reference.