workflows

To manage long-running application processes, you can configure workflows with specific commands, set up port waiting, and enable automated restarts to ensure persistent background services stay running.

You can restart a background service by triggering the restart command on the specific workflow. This applies new code changes by stopping the current process and starting an updated instance of the application workflow.

Yes, you can configure application workflows to wait for a specific port. The workflow process monitors the port and only reports as active once the designated port becomes available for webviews or consoles.

The best way to monitor background processes is by using status checks to view the current state and logs. This allows you to verify that your configured workflows are running without manually inspecting system processes.

You define output types when configuring the workflow by specifying webviews, consoles, or VNC. This directs the application process output to the appropriate interface for direct interaction or viewing.

To stop and remove application workflows, you use the removal command provided by the process manager. This safely terminates the background service and deletes its configuration from your active workflow list.