---
title: Troubleshooting
description: >-
  A page of real issues organized by symptom — label operation formatting
  mistakes, PR/MR not found, skill cannot execute, Epic not created, resuming
  from interruption
seo:
  image: /ogp.png
---
Headings are written as the symptom itself. If you arrived via search, you can read the matching heading directly and follow it to the fix.

## I tried to remove a label, but a strangely named label was added instead

If you run a command with `-l "-status::todo"` — prefixing the label name with `-` (a minus sign) with the intent to delete it — the existing label is not removed. Instead, a **separate, incorrect label** named `-status::todo` is created.

The cause is that the `-` character carries no deletion meaning in the `-l` option. It is treated as a literal part of the string, so the instruction becomes "attach a label named `-status::todo`."
Label swaps such as `status::todo → status::doing` are performed automatically by `implement-backlog` using `glab`/`gh` commands, but this formatting is easy to get wrong when operating manually.

There are two remedies.

- The correct syntax is `--unlabel status::todo`. Use `--unlabel` instead of `-l` when removing a label.
- For any incorrect labels that have already been created, delete them via the GitLab API
  (`DELETE /projects/:id/labels/:label_id`).

This label swap is part of the [status label state machine](/concepts/status-labels).

## Implementation is done, but I can't find the PR/MR

`implement-backlog` goes only as far as committing code; it does not create a PR/MR. PR/MR creation is handled by `review-issue`, and only when the blocker count reaches zero.

The most likely explanation is that `review-issue` simply has not been run yet. See [review-issue](/skills/backlog/review) for details.

## A `disable-model-invocation` error appears and the skill cannot execute

This is not a bug — it is an intentional constraint. Major skills that include hard-to-reverse operations are prevented from running on Claude's own judgment alone. They execute only when you enter the slash command yourself.

The full error text and the reasoning behind it are covered in [Installation](/getting-started/installation).

## No Epic is created in GitLab; a regular Issue with only labels is created instead

Using GitLab's Epic feature has prerequisites, and it is not available under personal account namespaces. In that case, NexusArchitect automatically falls back to a regular Issue + `type::*` labels + a task list.

For the prerequisites and the structure after the fallback, see [Prerequisites](/getting-started/prerequisites).

## I stopped mid-way and don't know where to resume

Progress is recorded in files and tracker labels, so running the same command again will pick up where it left off. Where each piece of state is stored and which command to use to check the current status is covered in [Interruption and Resume](/concepts/resume).

## I want to know how many tokens were used

Run `/architect:report-token-cost --once` to see the actual measured cost. For upfront estimates and ways to reduce costs, see [Understanding Token Costs](/concepts/token-cost).

---

You can read through a real end-to-end walkthrough of the issues listed here in [Practical Example: EASE](/tutorial).