# Sleep and wake

> Why a cloud workspace goes to sleep when it is not used, how it wakes up, how long that takes and what happens to schedules and Telegram while it sleeps.

Source: https://eggent.ai/docs/sleep/

A cloud workspace that has not been used for a while **goes to sleep**: its container stops and uses no server memory. This saves resources and takes nothing away from you.

## When it sleeps {#when}

After about **12 hours** without activity. Activity means your requests to the workspace: open chats, messages, file work, Telegram messages.

The workspace **does not sleep** if a [scheduled task](https://eggent.ai/docs/schedules.md) is due within the next half hour.

## How it wakes {#wake}

By itself, on the first request: you open the address in a browser, write in Telegram, or an [API](https://eggent.ai/docs/external-api.md) call arrives. Waking takes about **10 seconds**, after which the request runs as usual. Nothing is lost or repeated.

## Schedules {#schedules}

Scheduled tasks work during sleep too: the cloud wakes the workspace a couple of minutes before a run. So a daily digest or post arrives on time even if you have not visited for a week.

## What never sleeps {#always-on}

- [File sync](https://eggent.ai/docs/file-sync.md) with your computer — it works with the disk directly.
- The billing page and the sync page.

## Your own server {#self-host}

The open core has no sleep: Eggent runs as long as its container does.