Add more deployment FAQs (#13383)

Co-authored-by: Sarah Hughes <[email protected]>

content/docs/pulumi-cloud/deployments/faq.md

@@ -21,11 +21,23 @@ aliases:
 
 Deployments run on single-use virtual machines and compute and storage are never shared across runs. We designed our architecture to maximize isolation. In addition, security features like OIDC allow you to fine tune credential scope, lifetime, and expiration policies at a per-deployment level. It is also possible to use [self-hosted runners](/docs/pulumi-cloud/deployments/customer-managed-agents/) if you require additional isolation.
 
+## Deployment queue
+
+Deployments are queued on a first-come, first-served basis. If you have multiple deployments running at the same time, they will be queued and run in the order they were submitted.
+
+On a stack level, only one deployment can run at a time. On an organization level, the concurrency limit is determined by [SKU](/pricing/).
+
+Deployments will remain in the queue for a maximum of 7 days. If a deployment is not started within 7 days (if deployments are paused or the agent pool assigned to the stack is unavailable), it will be automatically removed from the queue and marked as `skipped`.
+
+## Paused deployments
+
+It is possible to pause deployments at the stack or organization level. Deployments that are already running are allowed to complete and are not paused. New deployments are queued, and will run when the stack or organization’s deployments are resumed.
+
 ## Dependency caching
 
 When using Pulumi-managed deployment agents, you have the option to speed up deployments using *dependency caching*.
 
-The caching method is simple: during the first deployment, the deployment agent will automatically detect downloaded dependencies using lock files, zip them up and store the archive in blob storage. During all subsequent deployments, agents will pull such an archive down and unpack it, saving time it would normally take to redownload those dependencies. When your dependencies change, deployment agents will automatically invalidate the old cache and create a new one.
+The caching method is simple: during the first deployment, the deployment agent will automatically detect downloaded dependencies using lock files, zip them up and store the archive in blob storage. During all subsequent deployments, agents will pull such an archive down and unpack it, saving time it would normally take to download those dependencies. When your dependencies change, deployment agents will automatically invalidate the old cache and create a new one.
 
 Caches are shared on the project level, so all stacks within a project can share the same cache. However, caches are fully isolated and never shared between customers.