Skip to content

Commit dee9669

Browse files
committed
fix(request-queue): Stress out the locking mechanism
1 parent df52238 commit dee9669

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

sources/platform/storage/request_queue.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -409,6 +409,15 @@ If the Actor processing the request fails, the lock expires, and the request is
409409

410410
In the following example, we demonstrate how we can use locking mechanisms to avoid concurrent processing of the same request across multiple Actor runs.
411411

412+
:::info
413+
The lock mechanism works on the client level, as well as the run level, when running the Actor on the Apify platform.
414+
415+
This means you can unlock or prolong the lock the locked request only if:
416+
417+
1. You are using the same client key, or
418+
2. The operation is being called from the same Actor run.
419+
:::
420+
412421
<Tabs groupId="main">
413422
<TabItem value="Actor 1" label="Actor 1">
414423

0 commit comments

Comments
 (0)