Run Troubleshooting

Support Guide

Resolve rejected profile names, normalized ordering, validation failures, partial pipelines, ignored options, and push errors.

Commandcusty run

Quick Command

custy run PROFILE [PROFILE ...] [OPTIONS]

troubleshootingpartial pipelinerecovery

Overview

Pipeline recovery begins by identifying the last completed stage. Do not assume that a failed profile left every file, reference, and remote unchanged.

The Profile Name Is Rejected

Use only commit, tag, push, dev, release, or full. Help text that lists internal names is ahead of the typed public argument.

A Combined Sequence Runs in a Different Order

The resolver globally orders deduplicated steps. This is expected and prevents the command-line order from placing push before preparation or commit.

Validation Stops the Pipeline

Fix the first reported condition. Later stages are intentionally not executed after required validation fails.

The Pipeline Stopped After Changing Files

Terminal

bash

git status -sb
git diff
git log -1 --decorate --stat
git tag --points-at HEAD

Inspect generated artifacts and backups. Determine the last completed stage before retrying; do not blindly rerun a partially completed release.

A Run Option Had No Effect

Review Run options and the effective project configuration. Explicit CLI remote selection has the highest priority; otherwise Custy applies the configured main, backup, synchronization, and push_to behavior.

The Editor Could Not Open in Docker

Use an interactive container so the bundled Micro, Nano, Vim, or Vi editor can access the terminal. Micro is the default container candidate. The project mount remains live while the editor is open.

Interactive Docker release

powershell

docker run --rm -it -v "${PWD}:/workspace" -w /workspace custy-prod:latest run release

Custy checks VISUAL and EDITOR first when enabled, then follows tool.custy.editor.candidates.container. An override must name an editor installed inside the container, not an editor available only on the host. See Editor configuration for identifiers and precedence. If a run already failed at EditFilesStep, inspect the generated commit and tag message files before retrying because GenerateArtifactsStep completed first.

An unavailable editor is skipped. A process that starts and then returns an error produces EDITOR_PROCESS_FAILED; Custy does not open another editor after the user may already have edited the message.

Progress Overlaps Terminal Editor Content

Current Custy releases suspend the live pipeline progress display while Micro, Nano, Vim, or Vi owns the terminal. The display resumes after the editor closes, so an EditFilesStep row should not cover or repeat inside the message buffer. This presentation handoff does not modify the file being edited.

If progress rows still appear inside the editor, first save or discard the message normally and exit the editor. Then verify that the local executable or container image matches the Custy build you intended to test:

Check the running Custy version

powershell

custy --version
docker run --rm custy-prod:latest --version

For a locally built image, rebuild the production target after updating the source, then retry with -it. An old executable or cached image can retain the earlier progress behavior even when the project files already contain the fix.

Push Failed

Use the Push troubleshooting guide and verify actual resolved remotes before retrying.

Overview​

The Profile Name Is Rejected​

A Combined Sequence Runs in a Different Order​

Validation Stops the Pipeline​

The Pipeline Stopped After Changing Files​

A Run Option Had No Effect​

The Editor Could Not Open in Docker​

Progress Overlaps Terminal Editor Content​

Push Failed​