Skip to Main Content

This is an IBM Automation portal for Integration 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
Workspace App Connect
Created by Guest
Created on Dec 7, 2023

Add transaccional support to the KafkaConsumer Node.

In the current behavior on the Kafka Consumer Node there are a couple of properties that manage the offset in the topic:
* Commit message offset in Kafka

* Wait for message offset commit to complete

However, the "commit" is done independently from the rest of the flow, so if the flow for instance is used to update a data base, and it turns out there is a problem with the data base that prevents the update, the KafkaConsumer node already committed the message offset and therefore we have lost that particular message.

In this case, the desired behavior would be to provide a property that marks the flow as transactional, so instead of committing the message offset immediately, the flow waits at the end and based on the result make the commit if the transaction was successful, otherwise keep the current offset, so the next time will try to process the same message again.

Idea priority Medium
  • Admin
    Ben Thompson
    Jan 5, 2024

    Idea review. Thank you for taking the time to raise this suggestion, and we agree that there would be benefit for the product in further exploitation of the possibilities that now arise with the Kafka transactional API. Specifically, we have considered providing the flow user the ability to decide the point within their flow logic where the Kafka commit should be executed (which it may be desireable for users to separate from the initial read/write with interim other actions being done by the flow)... in other words a separable KafkaCommit node. Similarly, a configuration setting to attempt to commit the Kafka transaction immediately before the flow's global unit of work is committed could be of value. Whilst there has already been discussion of some of these aspects on idea 462 (, we think there would be value for the community in tracking this idea separately (partly down to the nubmber of recent votes, and partly because the final externals may differ). We encourage any further comments on the various options floated here, and for now we are also updating the status of this idea to Future Consideration.