public sealed class DeadLetterPolicy : IMessage<DeadLetterPolicy>, IEquatable<DeadLetterPolicy>, IDeepCloneable<DeadLetterPolicy>, IBufferMessage, IMessage
Reference documentation and code samples for the Cloud Pub/Sub v1 API class DeadLetterPolicy.
Dead lettering is done on a best effort basis. The same message might be
dead lettered multiple times.
If validation on any of the fields fails at subscription creation/updation,
the create/update subscription request will fail.
Optional. The name of the topic to which dead letter messages should be
published. Format is projects/{project}/topics/{topic}.The Pub/Sub
service account associated with the enclosing subscription's parent project
(i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must
have permission to Publish() to this topic.
The operation will fail if the topic does not exist.
Users should ensure that there is a subscription attached to this topic
since messages published to a topic with no subscriptions are lost.
Optional. The maximum number of delivery attempts for any message. The
value must be between 5 and 100.
The number of delivery attempts is defined as 1 + (the sum of number of
NACKs and number of times the acknowledgement deadline has been exceeded
for the message).
A NACK is any call to ModifyAckDeadline with a 0 deadline. Note that
client libraries may automatically extend ack_deadlines.
This field will be honored on a best effort basis.
If this parameter is 0, a default value of 5 is used.
[[["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-07 UTC."],[[["\u003cp\u003eThe \u003ccode\u003eDeadLetterPolicy\u003c/code\u003e class in the \u003ccode\u003eGoogle.Cloud.PubSub.V1\u003c/code\u003e API provides functionality for handling messages that have failed delivery multiple times.\u003c/p\u003e\n"],["\u003cp\u003eThe latest version of the API documentation is \u003ccode\u003e3.23.0\u003c/code\u003e, with a history of versions going back to \u003ccode\u003e2.3.0\u003c/code\u003e, and version \u003ccode\u003e3.13.0\u003c/code\u003e is currently highlighted in the presented information.\u003c/p\u003e\n"],["\u003cp\u003eDead lettering of messages is performed on a best-effort basis, and a single message may be dead lettered multiple times.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eDeadLetterPolicy\u003c/code\u003e class allows for setting a \u003ccode\u003eDeadLetterTopic\u003c/code\u003e where undelivered messages will be published and a \u003ccode\u003eMaxDeliveryAttempts\u003c/code\u003e limit to determine how many times a message can be retried before being sent to the dead letter topic.\u003c/p\u003e\n"],["\u003cp\u003eThe service account associated with a subscription's parent project needs permission to publish to the designated dead-letter topic, and this topic should have a subscription attached to prevent message loss.\u003c/p\u003e\n"]]],[],null,[]]
