Troubleshooting

Kodmos only starts workflows that accept workflow_dispatch on the branch a deployment points at. When the trigger is missing, the box says the file has no workflow_dispatch trigger on that branch. Add it, push it to that branch, and pick the workflow again.

Before anything runs, Kodmos checks every deployment against its workflow file: required inputs need a value, a choice must be one of its options, a boolean true or false, and a number a number. If one is wrong, nothing starts and the message lists what to fix, so a release never stops halfway because of a typo.

Someone pushed to a branch after the lock, so its newest commit is no longer the one the event pinned. Nothing starts until DevOps re-pins the event to deploy what is there now, or the branch is put back.

Deploys with release tags push a kodmos/… tag to each repository, and workflows that run on tag pushes start for it too. Leave kodmos/** out of their tag filters; the flow editor lists the workflows that need it.

An environment limited to some branches refuses runs on a release tag. In the repository’s environment settings on GitHub, allow tags matching kodmos/**, or turn off release tags for the flow.

The organization deploys more repositories than its plan includes, and the 14-day grace period is over. Upgrade, or archive flows to get back under the limit. Planning and answering still work.

The GitHub App was removed from the organization on GitHub, so Kodmos can no longer see its repositories or start runs. The owner can reconnect it under Settings; flows, events and history are all still there.