---
title: "unknown"
description: "Error cause: unknown"
canonical: "https://studio.inttegro.dev/e/c-unknown"
format: inttegro-machine-docs/v1
language: "Ruby"
sdk_version: "v12.1.1"
reader_profile: optional
reader_manifest: "https://studio.inttegro.dev/machine/ruby/readers/index.json"
reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations."
preamble_estimated_tokens: 351
model_token_report: "https://studio.inttegro.dev/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: []
estimated_tokens: 1002
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Error cause: unknown This Ruby representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use unknown?

Use this page as orientation before selecting the narrower guide or reference that owns the implementation contract.

#### Q2. What is authoritative on this page?

Use this page for orientation; follow its canonical SDK, guide, API, or MCP links for exact contracts.

#### Q3. What page-specific constraint matters most?

Use the page to choose a canonical next source instead of treating summary material as a complete implementation contract.

#### Q4. Can Inttegro MCP materially help with this task?

No catalog ability is sufficiently specific to recommend for this page. Use the documentation directly; consult the MCP catalog only if the task later requires governed live account context or a supported operation.

#### Q5. How should the reader verify the answer and continue?

Select the narrowest linked guide or reference, apply its stated completion condition, and verify against authoritative resource state when the task changes data. Continue with [contact_customer_support](https://studio.inttegro.dev/machine/ruby/e/f-contact_customer_support.md) and [unknown_error](https://studio.inttegro.dev/machine/ruby/e/t-unknown_error.md) when those concerns enter scope.

## Document content

# unknown

Error cause indicating the error cause could not be determined.

## What this means

The Inttegro 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

```json
{
  "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://studio.inttegro.com/e/1889"
  }
}
```

## Related errors

- [unknown\_error](https://studio.inttegro.dev/machine/ruby/e/t-unknown_error.md) - Error type often paired with this cause
- [contact\_customer\_support](https://studio.inttegro.dev/machine/ruby/e/f-contact_customer_support.md) - Recommended action