Function never executes when browser window is closed when in queue

[peeter2]

Describe the bug

Somewhy the function never executes when the user is in queue and closes the browser window before the queue reaches to process his request.
Am I missing something or is this a bug? I need the visitor's request to be in queue even if he closes the browser window. I don't want unlimited concurrency, I need only one concurrent process. The function should eventually start when the queue reaches him (the function will send him an email notification) even if he has closed the browser window long ago.

I could not find any info on this from the documentation.

Thanks.

Have you searched existing issues? 🔎

• I have searched and found no existing issues

Reproduction

import gradio as gr

Screenshot

No response

Logs

No response

System Info

yes

Severity

I can work around it

[abidlabs]

Hi @peeter2 yes this is the intentional behavior. If a user uses your app through the Gradio queue, then they will automatically be removed if they close their browser window. This is to prevent the queue from exploding with very popular apps. What you could do potentially is to set queue=False for your event, in which case Gradio's queue is not used to manage your event, and your event is directly sent to FastAPI's API endpoint. In which case, concurrency is now controlled by FastAPI instead of Gradio. If you want to adjust the number of FastAPI threads, you can set the max_threads argument in launch()

[abidlabs]

Let me know if this workaround works for you @peeter2^