Codeflow troubleshooting
This page describes how to resolve issues that may occur while using Codeflow.
Workflow file is not displayed in the list
A workflow file may not appear in the workflow list in the console.
Workflow files must be located under .codeflow/workflows in the default branch to be recognized in the console.
▶️ Solution: Add the workflow YAML file under .codeflow/workflows in the default branch, then commit or merge it.
.codeflow/workflows/{workflow-file-name}.yml
Workflow is stuck in Waiting
A workflow execution may remain in the Waiting status and not proceed.
If no runner is running to process the workflow, or if the workflow runs-on value does not match the runner label, the workflow may remain in the waiting status.
▶️ Solution: In Action settings > Runners, check whether the runner is available. Also check whether the workflow runs-on value matches the --labels value specified when the runner was registered.
Runner VM cannot access external services
A runner VM may not be able to access Codeflow or Container Registry.
If the runner VM has no outbound internet route, it cannot access Codeflow repositories or Container Registry.
▶️ Solution: Attach a public IP or configure NAT so the runner VM can communicate externally, and check the outbound rules of the security group.
Image build step fails
The image build step in a workflow may fail.
If Docker is not installed on the runner VM that performs the image build, or if the Docker daemon is unavailable, the image build step fails.
▶️ Solution: Install Docker on the runner VM, check that the Docker daemon is running, and run the workflow again.