Skip to main content
Temporal Web is the Temporal UI included with the bundled Temporal deployment. It is useful for inspecting workflows and task queues, but it is not required for workflow execution.

​
Resource Profile

Temporal Web is a stateless UI service. It connects to Temporal Frontend to read workflow and namespace information. The bundled defaults should normally be left as they are. Scaling Temporal Web is rarely useful for Metoro Hub because workflow execution does not depend on the UI being available.

​
Restarts And Availability

Temporal Web pods do not store workflow state locally. They can be killed, restarted, or recreated at any time without losing durable workflow state or affecting workflow execution. If Temporal Web is unavailable, operators may temporarily lose the Temporal inspection UI, but Temporal workflows can continue as long as the Temporal server components and PostgreSQL persistence are healthy.

​
Before Tuning Web

If Temporal Web is slow or unavailable, check these signals before changing Web resources:
  • Temporal Web pod readiness, restarts, CPU throttling, and scheduling events.
  • Connectivity from Temporal Web to Temporal Frontend.
  • Frontend health and PostgreSQL persistence health.
  • Ingress or port-forward path used to reach the UI.
Tune Temporal Web only after the signal clearly points to the UI service itself. Do not scale Web to fix workflow execution issues.