unknown

Error cause indicating the error cause could not be determined.

What this means

The Commerce API encountered an error but couldn't identify the specific underlying category of failure that triggered it. This cause appears when an error occurs that doesn't map cleanly to established categories like authentication failures, parameter validation issues, or precondition violations. When you see this cause, it typically indicates an edge case, unexpected system state, or failure mode that requires engineering investigation to properly classify. For example, an unexpected database constraint violation when creating a new order that doesn't fall into parameter validation, or an unforeseen interaction between multiple systems when scheduling a payout.

The error is real and prevents your operation from completing, but the system's error classification logic couldn't determine whether it's an authentication problem, a validation failure, or something else entirely. Errors with unknown cause almost always result in a fix code of contact_customer_support, as proper resolution requires the engineering team to analyze logs and potentially add better error classification for this scenario.

Example error response

{
  "error": {
    "type": "unknown_error",
    "cause": "unknown",
    "code": "1889",
    "message": "unclassified error",
    "detail": "An error occurred that could not be classified into a known category. Our engineering team has been notified.",
    "fix_code": "contact_customer_support",
    "url": "https://commerce.zebo.dev/e/1889"
  }
}

Related errors

• unknown_error - Error type often paired with this cause
• contact_customer_support - Recommended action