---
title: Project Hibernated
description: Why a Free Flexkit project hibernates after a week without activity, and how to wake it up.
---

# Project Hibernated

A Free project that nobody uses for **7 days** hibernates. Its data is moved out of the database into encrypted storage, and its GraphQL API, automations and agent chat go offline until it is woken up. Nothing is deleted: waking it up restores every record, relationship and index exactly as it was.

Studio shows **Project Hibernated**, the dashboard shows a **Hibernated** badge, and API requests answer `403` with the code `PROJECT_HIBERNATED`.

Projects on Pro never hibernate.

## What Counts as Activity

Any of these keeps a project awake:

- An API request that succeeds, including Studio loading or editing records.
- An agent chat message or an automation run.
- A schema deploy or a Knowledge upload.
- Opening the project in the dashboard, or a change made there (members, tokens, settings).

Two days before a project hibernates, the team's owners get an email. Using the project in any of the ways above cancels it.

## Wake Up a Project

A project owner or developer can wake it up:

1. Open the project in the Flexkit dashboard.
2. Choose **Wake up project** on the Overview page.

Waking up usually takes a few minutes, depending on how much data the project has. The page shows the progress, and you get an email when the project is back online. You can leave the page meanwhile.

If you open the project while it is still going into hibernation, choose **Keep it awake** to stop it and bring it back online right away.

If a wake-up does not finish, the dashboard shows **Try again**. Your data stays safe in the archive whatever happens, and every attempt starts over from it. Flexkit is notified of failed attempts and retries them automatically.

## Keep a Project From Hibernating

Use it at least once a week, or upgrade it to [Pro](/docs/plans#pro).


---

[View full sitemap](/docs/sitemap.md)