diff --git a/sources/platform/actors/development/programming_interface/actor_standby.md b/sources/platform/actors/development/programming_interface/actor_standby.md index efa099fc16..5200546715 100644 --- a/sources/platform/actors/development/programming_interface/actor_standby.md +++ b/sources/platform/actors/development/programming_interface/actor_standby.md @@ -132,6 +132,8 @@ async def main() -> None: +After the readiness probe completes, the platform performs no further health checks against your Standby server. A run only restarts when the process exits or the run is migrated, so on unrecoverable errors, exit the process rather than swallow the error. That triggers the normal end-of-run restart path. + ## Determining an Actor is started in Standby Actors that support Actor Standby can still be started in standard mode, for example from the Console or via the API. diff --git a/sources/platform/actors/running/actor_standby.md b/sources/platform/actors/running/actor_standby.md index bd87983cb4..0d7ca1ea42 100644 --- a/sources/platform/actors/running/actor_standby.md +++ b/sources/platform/actors/running/actor_standby.md @@ -47,6 +47,7 @@ This approach can be useful if you cannot modify the request headers. ``` :::tip Scoped tokens + You can use [scoped tokens](/integrations/api#limited-permissions) to send standby requests. This is useful for allowing third-party services to interact with your Actor without granting access to your entire account. However, [restricting what an Actor can access](/integrations/api#restricted-access-restrict-what-actors-can-access-using-the-scope-of-this-actor) using a scoped token is not supported when running in Standby mode. @@ -63,6 +64,12 @@ it well. Please head to the Actor README to learn more about the capabilities of When you use the Actor in Standby mode, the system automatically scales the Actor to accommodate the incoming requests. Under the hood, the system starts new Actor runs, which you will see in the Actor runs tab, with the origin set to Standby. +## Health checks and stuck runs + +The platform checks a Standby run's readiness once, before marking it ready to receive requests. After that, the run is considered healthy and no further health checks are performed for the lifetime of the run. + +A Standby run restarts only when its process exits or the run is migrated to a different machine. If the server stays alive but stops responding, the platform does not detect the failure. For related Actor build guidance, see the [Standby development guide](../development/programming_interface/actor_standby.md#readiness-probe). + ## What is the timeout for incoming requests For requests sent to an Actor in Standby mode, the maximum time allowed until receiving the first response is _5 minutes_. This represents the overall timeout for the operation.