Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps 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.

Status Future consideration
Created by Guest
Created on Feb 7, 2024

Rerunning the single job does not create a new log but overlays the old log

Good evening, we have an idea  about the functioning of job rerun in the case of individual jobs not belonging to a Jobstream. When we rerun a single job within its flow it correctly creates a duplicate entry of the same job on the console with a new log generated on the new rerun. In the case in which we rerun a single job not contained within a Jobstream, the rerun is executed but a copy of the job with a new log is not created, but rather the same entry remains of the same original job and the new log generated overwrite the old log that existed before. In the old IWS 9.4 version of the product, this operation  created a new entry visible on the console with a new log, not covering the old log. And this was very useful  for troubleshooting purposes for example in the case of Jobs in error. It' s possible to implemet this feature also in te IWS 10.2 version ? Thanks a lot

Idea priority Medium
  • Admin
    Marco Cardelli
    Feb 21, 2024

    This is a defect and should be addressed with an APAR. Please open again a case and ask for L3 support. Contact me in case of problems at