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"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[[["\u003cp\u003eThe latest version available is 2.37.0-rc, with the webpage listing version options from 2.11.0 up to this latest release candidate.\u003c/p\u003e\n"],["\u003cp\u003eThis page provides documentation and version-specific links to the \u003ccode\u003ePullResponse\u003c/code\u003e struct within the Google Cloud Pub/Sub C++ library.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ePullResponse\u003c/code\u003e struct is associated with a handler, and message redelivery behavior depends on whether the \u003ccode\u003ehandler.ack()\u003c/code\u003e or \u003ccode\u003ehandler.nack()\u003c/code\u003e functions are invoked.\u003c/p\u003e\n"],["\u003cp\u003eThe behavior of redelivery is dictated by the subscription type, with exactly-once delivery subscriptions ceasing redelivery after a successful \u003ccode\u003ehandler.ack()\u003c/code\u003e, while best-effort subscriptions may redeliver even after successful acknowledgment.\u003c/p\u003e\n"],["\u003cp\u003eIf the handler is not an rvalue, \u003ccode\u003estd::move(handler).ack()\u003c/code\u003e or \u003ccode\u003estd::move(handler).nack()\u003c/code\u003e may need to be utilized, depending on if the message should be acknowledged or negatively acknowledged respectively.\u003c/p\u003e\n"]]],[],null,[]]
