multica-ai/multica · error
invalid %s %q; valid values: %s
Error message
invalid %s %q; valid values: %s
What it means
The value passed to --priority (or another issue enum field validated by validateIssueEnum) is not in the allowed set. The error lists the exact valid values, so this is purely an input-validation failure resolved by using one of the enumerated strings. Validation happens client-side before any API call.
Source
Thrown at server/cmd/multica/cmd_issue.go:415
}
return cols
}()
func validateIssueStatus(status string) error {
return validateIssueEnum("status", status, validIssueStatuses)
}
func validateIssuePriority(priority string) error {
return validateIssueEnum("priority", priority, validIssuePriorities)
}
func validateIssueEnum(field, value string, allowed []string) error {
for _, a := range allowed {
if value == a {
return nil
}
}
return fmt.Errorf("invalid %s %q; valid values: %s", field, value, strings.Join(allowed, ", "))
}
func init() {
issueCmd.AddCommand(issueListCmd)
issueCmd.AddCommand(issueGetCmd)
issueCmd.AddCommand(issuePullRequestsCmd)
issueCmd.AddCommand(issueChildrenCmd)
issueCmd.AddCommand(issueCreateCmd)
issueCmd.AddCommand(issueUpdateCmd)
issueCmd.AddCommand(issueAssignCmd)
issueCmd.AddCommand(issueStatusCmd)
issueCmd.AddCommand(issueReorderCmd)
issueCmd.AddCommand(issueCommentCmd)
issueCmd.AddCommand(issueSubscriberCmd)
issueCmd.AddCommand(issueRunsCmd)
issueCmd.AddCommand(issueRunMessagesCmd)
issueCmd.AddCommand(issueUsageCmd)
issueCmd.AddCommand(issueRerunCmd)View on GitHub (pinned to 2c0912b6ec)
Solutions
- Use one of the values listed in the error message verbatim (they are printed as the valid set).
- If sourcing the value from a variable, trim whitespace and lowercase it before passing: --priority "$(echo "$P" | tr -d ' ')".
- Omit --priority entirely to accept the default instead of guessing.
Example fix
# before multica issue create --title T --priority urgent # after multica issue create --title T --priority high
Defensive patterns
Strategy: validation
Validate before calling
# shell: whitelist before passing case "$PRIORITY" in urgent|high|medium|low) ;; *) echo "bad priority: $PRIORITY" >&2; exit 1;; esac # keep the list in sync with the values the error message prints
Type guard
func isValidPriority(v string, allowed []string) bool {
for _, a := range allowed {
if v == a {
return true
}
}
return false
} Prevention
- Source enum values from one place (config var) instead of scattering literals in scripts.
- Trim and case-normalize variable-sourced values before passing them as flags.
- Omit optional enum flags rather than guessing values.
When it happens
Trigger: Running `multica issue create --priority <bad>` or `issue update --priority <bad>` with a value not in validIssuePriorities — e.g. 'high ' with trailing whitespace, 'High' capitalized, 'urgent' (a plausible but invalid name), or an empty-string-adjacent typo.
Common situations: Scripts hardcoding a priority name that doesn't exist in this workspace; copying values from another tracker (Jira 'P1', Linear 'urgent'); case or whitespace mismatches from shell variable interpolation.
Related errors
- invalid status %q; valid values: %s
- --on-conflict must be one of: fail, overwrite, rename, skip
- runtime probe_result must be success or error
- --cutoff is required; use the hosted deployment time of the
- parse --cutoff as RFC3339: %w
AI-assisted analysis of multica-ai/multica@2c0912b6ec (2026-08-15).
Data as JSON: /api/errors/db5db8481d6e1c75.
Report an issue: GitHub.