@Karthik Kummera In a containerized Pega application (like on Pega Cloud 3 using Kubernetes), traditional requestor pools for service packages may not behave the same as in on-prem setups. Requestors are more dynamically managed by the container orchestration layer, so you may not see dedicated or persistent requestor pools for each service package. This means you typically cannot configure idle requestor counts or manually clear requestor pools as before. Instead, the system auto-scales based on demand, and requestors are recycled when not in use. However, you can limit the number of active requestors indirectly by configuring service-level concurrency (like max concurrent threads or connections) or using Kubernetes pod resource limits to control how many requests your services can handle at once