I have a microflow that gets triggered bij receiving messages on a Kafka stream, its purpose is to write this information to a secondary system. When the secondary system is not responding the microflow ends in an error event. I would expect this to cause the offset for the Kafka consumer to not increase and to retry the same message after some delay. However, it seems that the error event does not influence the actual outcome. Whenever the Microflow ends (end event ór error event) the offset is increased by one and the next message will be picked up and processed. Is there a way to not have this happen in the case of an error event and 'pause' the consumer until the current message can be processed succesfully?
asked
Maikel de Groot
1 answers
1
After further investigation I came to the conclusion that the error handling in the consumer code in the Kafka module is not fully implemented. An error is thrown and caught but there is no actual logic to process this which results in no practical difference between ending the On Receive microflow in an error and ending it in an error event.