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 webpage provides a comprehensive list of versions for `structgoogle::cloud::pubsub::PullResponse`, ranging from the latest release candidate `2.37.0-rc` down to version `2.11.0`."],["The content describes the behavior of message redelivery in the context of invoking `handler.nack()` or allowing `handler` to go out of scope, causing the service to redeliver the message."],["The page explains the difference between exactly-once delivery subscriptions, where the message is not redelivered after a successful `handler.ack()`, and best-efforts subscriptions, where redelivery may still occur."],["It also highlights that when a `handler` is not an rvalue, `std::move(handler).ack()` or `std::move(handler).nack()` might be necessary."],["The provided link leads to the Google Cloud documentation about exactly-once delivery."]]],[]]
