workflows

You can manage long-running application workflows by mapping a shell command to a named task, configuring wait-for-port options, and using lifecycle controls to restart or remove services when they fail or become unresponsive.

You can monitor listening ports by retrieving detailed workflow status and using the port reporting function to verify that your background services are active and accessible on the expected network ports.

Yes, you can configure a workflow with the waitForPort option to pause execution until the specified port is open, ensuring the service is fully ready to accept connections before proceeding.

The best way to handle misbehaving backend APIs is to inspect recent logs and port status, then restart the specific workflow to stabilize the runtime environment without disrupting other active services.

To remove legacy workflows that conflict with new services, use the workflow removal function to cleanly stop and delete unused processes, preventing port conflicts and stabilizing the deployment environment.

Workflow restart failures after dependency changes often occur when the expected port is already in use or blocked, requiring you to remove conflicting legacy workflows and verify port availability before reconfiguring.