Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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
Created by Guest
Created on Dec 16, 2021

Record cron task errors in a db table

It would be helpful if cron task errors could be recorded in a database table somewhere in Maximo.

Currently, the Runtime Error field in the cron task instance history does not get populated. That's due to a design flaw with the cron task framework in core Maximo. The Runtime Error field is only used when there are problems with the cron task engine, not the cron task itself, which does not make sense. That field has never been populated for any of our cron tasks, in any of our environments, despite there being lots of errors with our cron tasks.

Currently, there is no way to know that there were errors with cron tasks, other than reading the logs, which is very hard to do in a production environment because of all other stuff happening there.

Idea priority Medium