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
  1. Concepts
  2. Long-lived functions

Long-lived functions

Written by
Yandex Cloud
Updated at October 21, 2024

A long-lived function is one with a timeout of over ten minutes in its version settings. For the maximum possible timeout value, see Limits.

Note

This feature is in the Preview stage. To get access, contact tech support or your account manager.

The longer the function runs, the higher is the probability of related network failures. When invoking long-lived functions, we recommend using asynchronous invocation.

Forced termination of a long-lived function instanceForced termination of a long-lived function instance

In some cases, the service may forcibly terminate a long-lived function instance processing a call before the timeout specified in the function version settings is reached.

In such cases, the custom code of the function will receive a notification about the upcoming forced termination of the function instance. Such a notification is sent to the function ten minutes before the actual forced termination.

Once the notification about the upcoming forced termination of the function instance is sent:

  • The function instance has up to ten minutes to complete processing the current calls.
  • The function instance will no longer be receiving new calls.
  • The function instance will be forcibly stopped as soon as it completes processing all the current calls or after ten minutes, whichever comes first.

Warning

If there are less than ten minutes left before the timeout specified in the function version settings expires, no notification about the forced termination of the function instance will be sent to the function custom code.

Was the article helpful?

Previous
Asynchronous function invocation
Next
Function termination notifications
© 2025 Direct Cursus Technology L.L.C.