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
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Cloud Functions
  • Comparison with other Yandex Cloud services
    • Overview
    • Function
    • Invoking a function
    • Asynchronous function invocation
    • Long-lived functions
    • Function termination notifications
    • Networking
    • Mounting external resources to a function file system
    • Builder
    • Dead Letter Queue
    • Function logs
    • Backups
    • Quotas and limits
  • Tools
  • Pricing policy
  • Access management
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • The redrive policy
  • Use cases
  1. Concepts
  2. Dead Letter Queue

Dead-letter queue in Cloud Functions

Written by
Yandex Cloud
Updated at April 18, 2025
  • The redrive policy
  • Use cases

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

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

If no redrive policy is configured, the messages that the function 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 function 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 Yandex Message Queue trigger is configured when creating a source queue for messages that are processed by the triggered function.

The message keeps its ID after moving to the DLQ.

Use casesUse cases

  • Status monitoring of geographically distributed devices
  • Sensor reading monitoring and event notifications

Was the article helpful?

Previous
Email trigger
Next
Function logs
© 2025 Direct Cursus Technology L.L.C.