KB: service stuck "awakening" for too long

[Blargian]

Summary

From Ask AI coverage gaps:

Bot could not explain why Cloud services stay in “starting/awakening” for 30-60+ minutes, nor offer documented troubleshooting beyond pinging the service or opening a support ticket. Docs lack expected start-up timelines, common causes (large metadata, scaling, release upgrades), and self-service recovery steps, so the answer resorts to speculation and support escalation.

Adds a KB article on some reasons your service might potentially take longer than usual to start.

Checklist

• Delete items not relevant to your PR
• URL changes should add a redirect to the old URL via https://github.com/ClickHouse/clickhouse-docs/blob/main/docusaurus.config.js
• If adding a new integration page, also add an entry to the integrations list here: https://github.com/ClickHouse/clickhouse-docs/blob/main/docs/integrations/index.mdx

[vercel]

@Blargian is attempting to deploy a commit to the ClickHouse Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clickhouse-docs	Ready	Preview	Feb 9, 2026 9:16pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
clickhouse-docs-ru	Ignored	Preview	Feb 9, 2026 9:16pm
clickhouse-docs-zh	Ignored	Preview	Feb 9, 2026 9:16pm

[vercel]

Deployment failed with the following error:

The provided GitHub repository does not contain the requested branch or commit reference. Please ensure the repository is not empty.