Allow differentiating between failed event publications and ones that are currently processed

Hi,

we ran into another issue with multiple nodes (using jpa event publication), where one node tries to handle the event via the local application event publishing mechanism, whilst the other node tries to replay incompleted event (because it has not been marked as completed yet).
For now we mitigated the issue, by only replying events older than x seconds to avoid the same event handler to be triggered twice on different nodes.
I wonder, if it would be useful that any event handler either keeps a lock in the database while processing an event or uses a state field (wether the event is currently being processed).

What would be your recommendation?

Start by tracing the JPA event publication and incomplete-event replay paths described in the issue, including how multiple nodes select and mark publications. Compare database locking with a processing state, then clarify the intended behavior for concurrent handlers and replay timing. Done requires a decided recommendation or implementation scope that prevents duplicate handling across nodes.