Operate

Check service health

Use the health checks to decide when a server can receive work.

Use the two health checks

  • /health/live tells you that the program is running.
  • /health/ready tells you that the program is ready to receive work.

Recognise database recovery

In the signed 1.0.0 packages, /health/live can return status: recovering while the application rebuilds after a database failure. The response includes service and instanceId. After MySQL recovery, the instance ID may change even when the service process did not restart. An ID change alone does not prove a process restart or completed recovery. Keep the server out of traffic until /health/ready succeeds, then confirm a normal authenticated request.

Use Ready for traffic

A server can be running but not ready. It may still need a database, an update, or an AI service.

Set the load balancer to use the Ready check.

The System operations Servers view
Use this view with the health checks to understand the server state. Earlier development interface, captured 22 August 2026. Follow the written instructions for 1.0.0. Open the full image.

Know the healthy result

Live should succeed for each running process. Ready should succeed only when the service can accept its normal work.

System operations should show the expected servers as ready. New test work should leave the queue and reach a final state.

Protect the AI service

Only Workflow servers and trusted administrator networks should reach the private AI service.

Retry with care

Retry a request only when the connection failed or the error says it is safe. Do not repeat every model request automatically.

If a service is not ready

Keep it out of normal traffic. Follow Fix service readiness and storage problems.

Pūnaha Docs

Search the guides

Enter at least two characters.

    Product screen

    View the full screenshot