re-opening a study that is being closed

[pcrespov]

Currently closing a project takes some time because:

• project is locked
• closes services
• zip&uploads data
• closes sidecars

The closing procedure could be delayed ("soft-close") such that the user could reopen fast (~1mins). This is a typical behaviour of GC. We could

PROS

• user can reopen fast (e.g. if mistake)

  CONS:

• consumes resources (charged to user!)

### Sundae
- [ ] https://github.com/ITISFoundation/osparc-simcore/issues/4399
- [ ] disable projects close when going to dashboard @odeimaiz
- [ ] ensure logout triggers close @pcrespov
- [ ] add API to delay-close projects without switching off services

### Watermelon
- [x] https://github.com/ITISFoundation/osparc-simcore/pull/4349

[GitHK]

Possible issue

Locking can get messy

When the project is used there is a lock that blocks (for example the opening of the project by others) When "existing" the project and before letting the GC close it, the project cannot be considered as unlocked. Otherwise another user can open it and we might end up in unexpected territory.

We want locking to still work as it does not, only the user has the ability to open it before the real closing is done.

Closing Tabs

This needs to work when the tab is closed (meaning delay close cannot be sent by the frontend). The close will simply not be sent (or can we avoid this)?

---

Side effects for current proposal:

• if you have bad connectivity on the train and enter a tunnel that is 1:10 long (your project will be closed)
• if you want a collaborator to open the study they will take 1 extra more minute to open it

@pcrespov some of my inputs here