Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

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.

IBM Employees should enter Ideas at

Status Planned for future release
Created by Guest
Created on Feb 21, 2024

Increase timeout for Cognos Controller on Cloud & Excel Add-ins

Even when users are actively working on Excel for more than 60 minutes following a report refresh, the Add-ins prompt them to log out and re-login with their IBMid. This occasionally causes Excel to hang, forcing users to end the task via the Task Manager, relaunch Excel, and log back into Cognos.

A similar behavior is observed in the Cognos Controller on Cloud Classic Client as well. Please refer to the comments provided by the Business for additional context.

Furthermore, the session is not retained before timeout and after logout & re-launch. Users are required to restart the application and begin their work anew. Unfortunately, any unsaved data is lost in both the CCoC Classic Client and Excel. This is a significant concern that needs to be addressed.

We currently have a global user base of over 350 Cognos users. The persistent issue has been a source of considerable annoyance and frustration, especially during the month-end period when users are tasked with meeting strict deadlines. This pressing concern warrants immediate and thorough attention.

Needed By Month
  • Admin
    Maximilien de Chestret
    Mar 15, 2024

    Our understanding is that an interim solution has been implemented around time-out. In the next release we plan to implement a seamless re-log in after time out.

  • Guest
    Feb 21, 2024

    Beside increase timeout (currently 1 hour by default), please consider all these to the enhancement:
    1) The timeout should NOT just consider the CCoC activities (refresh / export etc), it should if user is actively on Excel. User usually continue to work on the CCoC retrieval report after refresh (e.g. analyse the number, prepare the report) and only start the next refresh after completing one task. It's not efficient to keep asking user to logout after refresh while working on the report and log on again when they need to refresh just to avoid the timeout error

    2) In the event of timeout, CCoC should kick user out of the CCoC (log off) and a pop-up message to notify user that the session is terminated due to timeout and request user to relog on. Currently it's showing user as "logon" status on the face of the excel, hence user encountered "object reference" error when they pressed F9/F10 without knowing that they have been log off.

    3) CCoC should NOT prompt for "IBMid logon screen" when user try to log off after idling for some time. "IBMid log on screen" should only applicable when user wanted to continue with the session.