Configure how long the application has to respond (ACK or NACK) to an incoming message. Note that this might be longer, or shorter, than the deadline configured in the server-side subscription.
The value 0 is reserved to leave the deadline unmodified and just use the server-side configuration.
[[["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 content provides documentation for the \u003ccode\u003eMaxDeadlineTimeOption\u003c/code\u003e across multiple versions, ranging from 2.11.0 to the latest release candidate 2.37.0-rc.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eMaxDeadlineTimeOption\u003c/code\u003e configures the duration an application has to acknowledge (ACK) or negatively acknowledge (NACK) an incoming message.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation notes that setting the value to \u003ccode\u003e0\u003c/code\u003e will leave the deadline unmodified, defaulting to the server-side configuration.\u003c/p\u003e\n"],["\u003cp\u003eThe deadline applies per message, extending the deadline repeatedly for a batch of N messages until it is delivered to the callback, at which point the deadline becomes immutable.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eMaxDeadlineTimeOption\u003c/code\u003e is an alias for the \u003ccode\u003estd::chrono::seconds\u003c/code\u003e type.\u003c/p\u003e\n"]]],[],null,[]]
