From 3571277b709873679a62782ada0453e6105a4543 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Franti=C5=A1ek=20Nesveda?= Date: Wed, 29 Jan 2025 12:25:30 +0100 Subject: [PATCH] feat: Add event data to `MIGRATING` event --- .../actors/development/programming_interface/system_events.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sources/platform/actors/development/programming_interface/system_events.md b/sources/platform/actors/development/programming_interface/system_events.md index f5dfb1591..2202c92f7 100644 --- a/sources/platform/actors/development/programming_interface/system_events.md +++ b/sources/platform/actors/development/programming_interface/system_events.md @@ -32,7 +32,7 @@ The following table outlines the system events available: | Event name | Payload | Description | | -------------- | ------- | ----------- | | `cpuInfo` | `{ isCpuOverloaded: Boolean }` | Emitted approximately every second, indicating whether the Actor is using maximum available CPU resources. | -| `migrating` | N/A | Signals that the Actor will soon migrate to another worker server on the Apify platform. | +| `migrating` | `{ timeRemainingSecs: Float }` | Signals that the Actor will soon migrate to another worker server on the Apify platform. | | `aborting` | N/A | Triggered when a user initiates a graceful abort of an Actor run, allowing time for cleanup. | | `persistState` | `{ isMigrating: Boolean }` | Emitted at regular intervals (default: _60 seconds_) to notify Apify SDK components to persist their state. |