Gitpod / Ona Environment Disappeared or Deleted: Archive and Auto-Delete Explained

How to fix it

Try these in order — the most common fix is first.

1. 1. Unarchive it

   Copy steps
   1. Open User settings > Archived sessions
   2. Select the environment or open its row actions menu
   3. Choose Unarchive
   Did this fix it? Yes No

2. 2. Prevent a repeat

   Copy steps
   1. Push work to Git regularly
   2. On Enterprise, ask an admin to extend archive (1-30 days) or auto-delete (1-4 weeks, or never)
   3. Archive manually with: ona environment archive <id-or-name>
   Did this fix it? Yes No

Symptoms

An environment you left idle is missing from your list, or its content is gone.

Why it happens

• Core archives stopped environments after 3 days of inactivity
• Archived environments are auto-deleted 4 days after archival on Core
• An org policy may shorten retention over your personal setting
• Someone deleted it manually (permanent)

This guide also covers

• gitpod workspace deleted
• ona environment disappeared
• gitpod workspace archived
• gitpod auto delete

Other Gitpod errors

• Gitpod Classic Shutdown: How to Migrate to Ona Before October 15
• Ona (Gitpod) Credits Running Out: How OCUs Are Used
• Gitpod Classic Billing: Usage Limit Reached, Credits and Invoices
• Ona AWS Runner Failed: ROLLBACK_COMPLETE and ECS Circuit Breaker Errors
• Ona Environment Fails: AWS account policy blocks ssm:SendCommand
• Ona Environment Starts Then Stops in Seconds (Custom CA Bundle)
• Ona GCP Runner Not Connected: Terraform, Health Check and Zone Resource Errors
• Gitpod Classic JetBrains Gateway Not Working or Workspace Won't Start