Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Serverless Containers
  • Comparison with other Yandex Cloud services
    • Overview
    • Container
    • Invoking a container
    • Runtime environment
    • Networking
    • Mounting external resources to a container file system
    • Long-lived containers
    • Container termination notifications
    • Dead Letter Queue
    • Container logs
    • Backups
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Audit Trails events
  • Release notes
  • FAQ
  1. Concepts
  2. Dead Letter Queue

Dead Letter Queue in Serverless Containers

Written by
Yandex Cloud
Updated at February 27, 2023

The Dead Letter Queue (DLQ) is a queue for messages that could not be processed by a triggered Serverless Containers container. A message is considered processed if the container that received it ended successfully. Messages moved to the DLQ are stored there for further analysis.

If the container failed to process a message within the specified number of attempts, the message is moved to the DLQ. The number of container invocation attempts and the DLQ are specified in the redrive policy. The DLQ in Serverless Containers can only be a standard queue.

If no redrive policy is configured, the messages that the container failed to process are deleted.

The redrive policyThe redrive policy

The redrive policy defines the conditions for moving messages to the DLQ.

To configure the redrive policy for all triggers except a trigger for Yandex Message Queue, specify the following when creating a trigger:

  • The queue to move messages to.
  • service account with rights to write messages to the queue.
  • The time after which the container will be invoked again if the current attempt fails.
  • The number of invocation retries before the trigger moves a message to the queue.

The redrive policy for the trigger for Yandex Message Queue is configured when creating a source queue for messages that are processed by the triggered container.

The message keeps its ID after moving to the DLQ.

Was the article helpful?

Previous
Email trigger
Next
Container logs
Yandex project
© 2025 Yandex.Cloud LLC