Currently the messages are acknowledged when they are received before the subscribers (consumers) process them, that could lead to issues in case any error happens when processing them.

See QuarkusCloudEventPublisher class and https://github.com/kiegroup/kogito-runtimes/pull/910.

It should be tested and validated cases when error happens when processing the messages, because probably the stream that receives messages would stop in case of any exception, this should be avoided conintue to receive messages but with a nack or whatever.

One approach could be to have an abstraction of Message that would pass to the subcribers to proper handle the ack or nack either on Quarkus or Spring.