multica-ai/multica · error

resolve issue: %w

Error message

resolve issue: %w

What it means

Before listing an issue's pull requests, the CLI must resolve args[0] (an issue reference — ID, key, or similar accepted form) to a concrete issue ID via resolveIssueRef. That resolution failed; the %w carries the reason (no match, ambiguous match, or a lookup API error). This is the same resolution step every issue subcommand performs.

Source

Thrown at server/cmd/multica/cmd_issue.go:755

		}
		rows = append(rows, row)
	}
	cli.PrintTable(os.Stdout, headers, rows)
	return nil
}

func runIssuePullRequests(cmd *cobra.Command, args []string) error {
	client, err := newAPIClient(cmd)
	if err != nil {
		return err
	}

	ctx, cancel := cli.APIContext(context.Background())
	defer cancel()

	issueRef, err := resolveIssueRef(ctx, client, args[0])
	if err != nil {
		return fmt.Errorf("resolve issue: %w", err)
	}

	var result map[string]any
	if err := client.GetJSON(ctx, "/api/issues/"+url.PathEscape(issueRef.ID)+"/pull-requests", &result); err != nil {
		return fmt.Errorf("list issue pull requests: %w", err)
	}

	output, _ := cmd.Flags().GetString("output")
	if output == "json" {
		return cli.PrintJSON(os.Stdout, result)
	}

	prs, _ := result["pull_requests"].([]any)
	printIssuePullRequestsTable(normalizePullRequestList(prs))
	return nil
}

func normalizePullRequestList(raw []any) []map[string]any {

View on GitHub (pinned to 2c0912b6ec)

Solutions

1. Read the wrapped error — not-found vs ambiguous vs transport failure each have different fixes.
2. Confirm the issue exists with `multica issue list` (or `issue get <ref>`) and copy the exact key/ID.
3. If ambiguous, use the unambiguous numeric/canonical ID.
4. If transport-related, fix connectivity/auth first (same steps as any API error).

Example fix

# before
multica issue pull-requests MUL-9999   # deleted issue
# after
multica issue list --limit 20          # find the live key
multica issue pull-requests MUL-4252

# confirm the ref resolves before the subcommand
multica issue get "$REF" --output json >/dev/null 2>&1 \
  || { echo "issue ref does not resolve: $REF" >&2; exit 1; }

When it happens

Trigger: Running `multica issue pull-requests <ref>` where <ref> is a typo'd issue key, an ID that was deleted, a key that matches multiple issues, or when the resolution lookup itself hit a network/auth failure.

Common situations: Script reusing an issue key captured before the issue was renamed/moved/deleted; copy-paste truncating the key; parallel sessions where the issue was just deleted.

Related errors

• no agent found matching %q
• ambiguous agent %q; matches: %s
• resolve assignee: %w
• list issue pull requests: %w
• multica CLI version not reported by daemon

AI-assisted analysis of multica-ai/multica@2c0912b6ec (2026-08-15). Data as JSON: /api/errors/2dfd77b2ea724c2c. Report an issue: GitHub.