workflows

To manage background processes, you configure workflows that automatically start and keep long-running services active. This provides lifecycle control for web servers and backend tasks, ensuring they auto-restart after installations or configuration changes without manual tracking.

Restart a backend service by instructing the workflow manager to restart the specific workflow. This applies your environment variable updates to the running app, confirms the service restarted correctly, and displays recent console logs and open ports.

Yes, you can monitor console logs and open ports for a running application. The workflow manager provides operational visibility by inspecting recent output and displaying the specific ports the service is listening on to confirm it started correctly.

The best way to configure a persistent web server workflow is to define a workflow name, shell command, and correct wait-for-port and output-type alignment. This ensures the server stays active, auto-restarts after changes, and exposes the web app for access.

Your workflow may not start correctly if the wait-for-port and output-type or port alignment is misconfigured. Ensure you provide a valid workflow name and shell command, then inspect the recent console logs and open ports to diagnose the startup failure.

Yes, this workflow manager works with TUIs and long-running backend tasks. It applies to web servers, backend services, and other persistent tasks that must stay active, providing lifecycle control, discovery, and operational visibility for various long-running applications.