Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Future consideration
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Oct 22, 2019

Server-enforced agent concurrency limits

I propose a feature whereby agents can be configured in the server UI to have concurrency limits. Currently, concurrency limits can be specified in processes for multiple-component deployments. It would be useful to be able to specify how many Component Processes can run on a given agent at any one time. This would tie in with the workload assessment for Pools when assigning an agent, but also force processes to become 'queued' waiting for an available slot for shared agents. This would also allow administrators to provide some protection for agents that are shared among various users - at present, agents will just keep processing new component requests until they run out of resources, but with configurable limits in place, this would also guarantee a minimum level of performance.

Idea priority Low
RFE ID 137500
RFE URL
RFE Product UrbanCode Deploy
  • Guest
    Apr 16, 2021

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

  • Guest
    Jan 25, 2021

    Dev team investigating in Q1 2021