Database Asleep

database-asleep · 409

The database is asleep and the call didn't ask to wake it, so the API opened no tunnel.

Opening a tunnel never wakes a database silently. flag names the CLI flag that wakes it. The CLI exits with code 5.

Besides the members every error carries, this type adds service, environment and flag.

Common causes

  • The database's environment went to sleep, and the database with it.
  • The tunnel dropped for long enough that the database fell asleep before it opened again.

How to fix the call

  • Run the command again with --wake: ghaym cloud connect orders-db --env staging --wake.
  • Through the API, send wake: true in the body that opens the tunnel.
  • While the tunnel is open, the database counts as in use and stays awake.

Example response

json
{
  "type": "database-asleep",
  "title": "Database Asleep",
  "detail": "orders-db is asleep in staging. Add --wake to wake it and connect.",
  "service": "orders-db",
  "environment": "staging",
  "flag": "--wake",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/tunnels",
  "method": "POST",
  "instance": "POST /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/tunnels",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/database-asleep"
}