How does AppStream Disconnect Timeout state affect my app

Question

We're migrating an app that currently saves its state and users' work every 10 minutes. Persistent storage is configured. I wonder what happens in a situation where a user accidentally disconnects before the next 10 minutes (let's assume that 8 minutes of work has passed and the user closes the browser tab). Will our application stay alive, so to say, and be able to write to S3? I understand that session is in a Disconnect timeout state but will our app be able to save the last work made by a user in this state? Or does the instance enter some kind of hibernate state?
![Enter image description here](/media/postImages/original/IM8E6sy8IsQn2Pf_HgRw5Lew)

Accepted Answer

Hey Les,

**Disconnect timeout in minutes** keeps the AppStream session active after the user disconnects. So if you have configured for 10 mins, the session remains running for the next 10 mins. There is no concept of hibernate state here. Now, it really depends on your application whether it can write to S3 storage when there is no user interaction. If it can, you are good.

My recommendation is to test this out which i believe is quite straightforward. Set the timeout to 10 mins and disconnect the session to see how the application behaves.

Hope it helps,

-arun.

How does AppStream Disconnect Timeout state affect my app

Relevant content