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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Feb 20, 2024

Introduce timeout for process steps

- We recently saw a case where a deployment process was stuck at one particular step for 3+ hours due to some issues.

- It's a good idea to introduce a new step property "timeout" that can kill the step that is stuck after the mentioned timeout period.

- When some one is creating a deployment process - he/she should be able to mention this timeout value/property for all the individual steps in the deployment process' workflow. 

- If not possible to implement for all the step's plugins, please do it at least for shell, groovy plugins (where some code gets executed).

- This is really a useful feature that can prevent deployments getting stuck leading to high deployment times violating SLA's.


Idea priority High
  • Admin
    Daniel Cappon
    Apr 16, 2024

    In development, planned for 8.1.1 release

  • Admin
    Randy Langehennig
    Mar 21, 2024

    Thank you for submitting this idea. Our development team is reviewing your idea request and we will be in touch with additional questions or comments in the near future.