Skip to main content
Use explicit low-code admission when one section of a Component needs a dynamic concurrency key. api.concurrencyLimit() returns whether it acquired a slot; it does not automatically enqueue work that cannot enter.

Explore the behavior

Bounded read example

This Component requires write-capable execution because acquiring a coordination slot changes coordination state. The business query itself is read-only. Replace the database name with an accessible Table and keep execution time below the 60-second permit lifetime.
The caller can report busy, retry explicitly, or schedule a Job.

Ownership and lifetime

Release exactly once after successful admission, through the same runtime invocation. Do not release when admission returned false. For separate SDK requests, use the same explicit leaseOwnerId for acquisition and release; choose a unique owner for each execution. The TTL is in seconds. Reusing an owner does not renew the lifetime; finish before expiry. This bounds concurrency while the permit is valid. It does not make business effects idempotent. For a whole background Job, prefer its managed concurrency policy. For exact arguments, see api.concurrencyLimit() and api.releaseConcurrencyLimit().
Last modified on November 8, 2026