# Session Inactivity Timeout
By **default**, your Appetize session will end after **2 minutes** of inactivity. You can modify the default app timeout, or specify a timeout for a specific app build by following the steps below:
## Default App Timeout
Navigate to [**Organization -> Session Defaults**](https://appetize.io/organization/session-defaults) **->** **Session Timeout**
Default App Session Timeout
## App Build Specific Timeout
Navigate to your [**Apps Dashboard**](https://appetize.io/apps) **-> Select** your preferred **app -> Select the build** you want to modify **-> Settings -> Session timeout**
Select the App you want to modify
Select the build you want to modify
Build Specific Inactivity Timeout
{% hint style="info" %}
You can also[ set](https://docs.appetize.io/rest-api/create-new-app)/[update](https://docs.appetize.io/rest-api/update-existing-app) the inactivity timeout of your app with our [REST API](https://docs.appetize.io/rest-api) when uploading your app.
{% endhint %}
## What's the behavior if you reach your concurrency limit?
When a user launches Appetize and the maximum concurrency limit has been reached, they will be placed in a virtual 'queue' and wait until additional capacity becomes available:
Sample of reaching the concurrency queue in our demo experience
As soon as a device becomes available, the queued users will be granted access, allowing them to continue as usual.
