If the application invokes handler.nack() or allows handler to go out of scope, then the service will redeliver the message.
With exactly-once delivery subscriptions, the service will stop redelivering the message once the application invokes handler.ack() and the invocation succeeds. With best-efforts subscriptions, the service may redeliver the message, even after a successful handler.ack() invocation.
If handler is not an rvalue, you may need to use std::move(handler).ack() or std::move(handler).nack().
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-14 UTC."],[[["The latest version available is 2.37.0-rc, which can be found in the reference documentation for `structgoogle::cloud::pubsub::PullResponse`."],["This page provides version-specific documentation for `PullResponse`, ranging from version 2.11.0 up to the latest release candidate."],["The `PullResponse` relates to the response received during a blocking pull operation."],["Message redelivery will occur if the application invokes `handler.nack()` or allows the handler to go out of scope."],["The behavior of message redelivery after a successful `handler.ack()` depends on whether the subscription uses exactly-once delivery or best-effort delivery, with best-effort potentially redelivering even after acknowledgement."]]],[]]
