# Limit worker process to work on only one workflow, and limit workflow to be executed by only one worker **URL:** \ **Category:** Community Support\ **Created:** [September 8, 2025, 8:52pm UTC](https://community.temporal.io/t/limit-worker-process-to-work-on-only-one-workflow-and-limit-workflow-to-be-executed-by-only-one-worker/18307 "2025-09-08T20:52:53Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\ **Post date:** [September 12, 2025, 6:37pm UTC](https://community.temporal.io/t/limit-worker-process-to-work-on-only-one-workflow-and-limit-workflow-to-be-executed-by-only-one-worker/18307/3 "2025-09-12T18:37:34Z")
> [@Does Temporal Typescript support workflow session](https://community.temporal.io/t/does-temporal-typescript-support-workflow-session/15236/6): > > I see. The main session feature is the ability to limit the number of such sequences of activities that can run in parallel. The session uses the following design and you can try to implement it yourself: Each process creates a separate worker with fixed parallelism (for example 1). Let’s call its task queue “process-lock”. Each process listens on a host specific task queue. For example, “host1”. To start the sequence of activities invoke “lock-process” activity at “process-lock” task queue. T… --- _[View the full topic](https://community.temporal.io/t/limit-worker-process-to-work-on-only-one-workflow-and-limit-workflow-to-be-executed-by-only-one-worker/18307)._