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:
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Make spectrum conductor token viability duration configurable.
When we schedule jobs over the weekend to run for Monday morning, the jobs do not run on Monday morning as expected, but give "Expired Credentials" error. These credentials do not expire as they are service accounts. This happens also for Admin account.
We do weekend patching and occasionally, we have issue with patching and the ascd service may be down overnight after patching. It looks like when acsd is down for 8+ hours it can't renew users credentials in the file schedule_users.yaml.
Can we adjust the duration (Looks like it is based on token viability) so that we can prevent this issue of scheduled jobs not running due to expired credentials.
Do not place IBM confidential, company confidential, or personal information into any field.