Protocols
Saved & recent

Consumer acknowledgment

Also called: consumer ack, message acknowledgment

A consumer acknowledgment tells a messaging system that a particular delivery has reached the application’s chosen completion point. With manual acknowledgments, the consumer decides when to send that signal. If a connection fails before acknowledgment, the system may make the message available for redelivery.

For example, a worker can acknowledge a job after saving its result. A crash after saving but before acknowledging can still cause duplicate work, so the saved effect needs suitable protection. A broker confirming a publisher’s submission is a different event: it does not mean a consumer has finished processing.

Read first
Message broker
Related
Delivery semantics, Dead-letter queue, Backpressure
Further reading
RabbitMQ — Consumer Acknowledgements and Publisher Confirms
broker worker deliver job save result crash window worker acknowledgment possible redelivery after crash publisher confirm · separate upstream step
A worker saves its result before sending the consumer acknowledgment. A crash after commit but before ACK can lead to redelivery and a repeated effect. The dashed arrows show alternative failure handling; publisher confirmation does not establish consumer completion.

View in the full Protocols collection