# minimum-seats-available behaviour

**URL:** <https://support.openanalytics.eu/t/minimum-seats-available-behaviour/2963>\
**Category:** ShinyProxy\
**Created:** [August 1, 2024, 9:37am UTC](https://support.openanalytics.eu/t/minimum-seats-available-behaviour/2963 "2024-08-01T09:37:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![GrumpyBadger](https://support.openanalytics.eu/user_avatar/support.openanalytics.eu/grumpybadger/32/1047_2.png) [@GrumpyBadger](https://support.openanalytics.eu/u/GrumpyBadger)\
**Post date:** [August 1, 2024, 9:37am UTC](https://support.openanalytics.eu/t/minimum-seats-available-behaviour/2963/1 "2024-08-01T09:37:31Z")

</div>

When you specify a minimum number of containers to be ready for use with the minimum-seats-available parameter, is there any logic to which container will be allocated to a user first?

We have an app which has a long startup time. Sometimes, the first person gets in fine but the second person to log in has a long wait before the container is ready. I’m guessing that they’re being allocated the newly-created container instead of one of the older ones. Could this be the case?

Ideally, a user should always be given the oldest container.

---

<div class="post-metadata">

**Author:** ![tdekoninck](https://support.openanalytics.eu/user_avatar/support.openanalytics.eu/tdekoninck/32/1079_2.png) [@tdekoninck](https://support.openanalytics.eu/u/tdekoninck)\
**Post date:** [August 5, 2024, 7:44am UTC](https://support.openanalytics.eu/t/minimum-seats-available-behaviour/2963/2 "2024-08-05T07:44:25Z")

</div>

Hi, currently there is no way to control the assignment to a container. The seats are added to a pool, but in no specific order.

You mention `a long wait before the container is ready.`, do these users see the ShinyProxy loading screen or a loading screen of the app (or simply a white page)?  
If they see the ShinyProxy loading screen, this means that a seat is not immediately available for the user, either because there are not enough containers or because a container is still starting up. In this case, I guess you have to increase the `minimum-seats-available`.  
In the other case, where the app still has to load/boostrap, this is the expected behavior and _some_ user will always have to for this bootstrap. The best solution here is to inspect your Shiny app and make sure everything is loaded/prepared on startup.
