Skip to main content

Service Lifecycle

Service detail pages are used to operate catalog services after deployment.

Service Detail Page​

The page can include:

  • Status summary.
  • Generated URL.
  • Overview tab.
  • Live logs tab.
  • Settings tab.
  • Service details.
  • Dependencies.
  • Controls.
  • Size panel.
  • Domains.
  • Delete preview.

Status And Actions​

StatusTypical Actions
runningOpen URL, add domain, review logs, resize if needed.
sleepingWake manually or open the URL and wait.
stoppedStart the service when needed.
failedRead recovery guidance, open logs, retry after fixing the cause.
deployingWait and watch logs.
upgradingWait for the resize or update to complete.
awaiting confirmationWait for deletion flow to complete or follow the confirmation UI.

Start And Stop​

Use stop when:

  • The service is temporary.
  • You want to pause non-production usage.
  • The owner confirms it is safe to pause.

Use start when:

  • Users need the service again.
  • A stopped dependency is required by another workload.

Stopping a stateful service does not replace backup or recovery planning.

Wake​

Sleeping services can wake on demand.

Use Wake service when:

  • You are about to demo the service.
  • You need it warm before sharing a link.
  • You want to confirm it still starts cleanly.

Retry​

Use retry after correcting the likely cause of a failed deployment.

Before retry:

  • Read the logs.
  • Check required variables.
  • Check plan and quota.
  • Check service-specific setup notes.

Resize​

Supported first-party services can preview and apply size changes.

Resize only after:

  • Preview is allowed.
  • Billing impact is understood.
  • Storage growth warning is accepted when applicable.
  • The service owner approves the change.

Domains​

Services with web interfaces can have custom domains.

Use the same domain flow as applications:

  1. Confirm generated URL works.
  2. Add custom domain.
  3. Copy the records shown by the UI.
  4. Click Check now.
  5. Wait for active status.

Dependencies​

If a service has dependencies, they appear on the overview tab.

Do not treat dependencies as unrelated services. They are often managed as part of the parent service.

Service Runbook​

For production service changes:

  1. Confirm owner.
  2. Confirm environment.
  3. Check current status.
  4. Make one change.
  5. Watch logs.
  6. Open URL.
  7. Check billing usage.
  8. Record the change reason.