> ## Documentation Index
> Fetch the complete documentation index at: https://ai-kb.automationanywhere.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 一般的な API エラー

> API エラーのトラブルシューティングのアドバイス

この記事は、EKB のクラウド プラットフォームを利用するときに発生する可能性のある最も一般的な API エラーを理解するのに役立ちます。さまざまな HTTP ステータス コードと特定のエラー コードの詳細が表示され、これらの問題を効果的に解決するための重要なトラブルシューティング手順が提供されます。エラー応答の形式と API の使用に関連する一般的な落とし穴を理解することで、エラーを処理し、開発エクスペリエンスを向上させるための準備が整います。

## エラー応答フォーマット

すべての API エラーは一貫した形式に従います。

```json theme={null}
{
  "status_code": 400,
  "error": {
    "code": "ERROR_CODE",
    "message": "Human-readable error message"
  },
  "detail": "Additional error details (optional)"
}
```

一部のエラーには次のものも含まれる場合があります。

* `error_id`: エラーを追跡するための一意の識別子
* `invalid_fields`: 検証に失敗したフィールドのリスト (検証エラーの場合)

## HTTP ステータス コード

### 400 不正なリクエスト

無効な入力または不正な形式のリクエストによるクライアント側のエラー。

<AccordionGroup>
  <Accordion title="VALIDATION_ERROR">
    **エラー コード**: `VALIDATION_ERROR`
    **ステータス コード**: `400`

    **説明**: リクエストの検証に失敗しました。リクエスト内の 1 つ以上のフィールドが無効です。

    **一般的な原因**:

    * 必須フィールドが不足しています
      * 無効なフィールド形式 (無効な電子メール、日付形式など)
      * 許容範囲外のフィールド値
      * 無効なデータ型

    **応答例**:

    ```json theme={null}
    {
      "status_code": 400,
      "error": {
        "code": "VALIDATION_ERROR",
        "message": "Invalid input data",
        "invalid_fields": ["email", "project_id"]
      }
    }
    ```

    **トラブルシューティング**:

    1. `invalid_fields` 配列を確認して、問題のあるフィールドを特定します
    2. API ドキュメントのフィールド要件を確認します。
    3. データ型が予期される形式と一致することを確認します
    4. 必須フィールドがすべて入力されていることを確認します
  </Accordion>

  <Accordion title="INVALID_API_KEY">
    **Error Code**: **PLACEHOLDER\_1**\
    **Status Code**: **PLACEHOLDER\_2**

    **Description**: The provided API key is invalid or malformed.

    **Troubleshooting**:

    1. Verify the API key is correctly copied (no extra spaces)
    2. Check if the API key is active in **My Account** > **API Keys**
    3. Ensure you're using the correct API key for your environment
    4. Regenerate the API key if necessary
  </Accordion>

  <Accordion title="INVALID_CREDENTIALS">
    **Error Code**: **PLACEHOLDER\_3**\
    **Status Code**: **PLACEHOLDER\_4**

    **Description**: Authentication credentials are invalid.

    **Troubleshooting**:

    1. Verify email and password are correct
    2. Check if account is locked or disabled
    3. Try resetting your password
    4. Ensure you're using the correct authentication method
  </Accordion>

  <Accordion title="INVALID_OR_EXPIRED_JWT_TOKEN">
    **Error Code**: **PLACEHOLDER\_5**\
    **Status Code**: **PLACEHOLDER\_6**

    **Description**: The JWT token is invalid, expired, or malformed.

    **Troubleshooting**:

    1. Refresh your authentication token
    2. Log out and log back in
    3. Check token expiration time
    4. Verify token is being sent in the correct header format
  </Accordion>
</AccordionGroup>

### 401 不正

認証が必要か、認証に失敗しました。

<AccordionGroup>
  <Accordion title="AUTHENTICATION">
    **Error Code**: **PLACEHOLDER\_7**\
    **Status Code**: **PLACEHOLDER\_8**

    **Description**: Authentication is required to access this resource.

    **Troubleshooting**:

    1. Ensure you're logged in
    2. Check if your session has expired
    3. Verify authentication headers are included in the request
    4. Re-authenticate if necessary
  </Accordion>

  <Accordion title="INVALID_BEARER_TOKEN">
    **Error Code**: **PLACEHOLDER\_9**\
    **Status Code**: **PLACEHOLDER\_10**

    **Description**: The Bearer token provided is invalid.

    **Troubleshooting**:

    1. Verify the token format: **PLACEHOLDER\_11**
    2. Check if the token has expired
    3. Regenerate authentication token
    4. Ensure token is not revoked
  </Accordion>

  <Accordion title="EMAIL_IS_NOT_VERIFIED">
    **Error Code**: **PLACEHOLDER\_12**\
    **Status Code**: **PLACEHOLDER\_13**

    **Description**: Email address has not been verified.

    **Troubleshooting**:

    1. Check your email for verification link
    2. Request a new verification email
    3. Verify email address is correct
    4. Check spam/junk folder
  </Accordion>
</AccordionGroup>

### 403 禁止

権限が不十分なため、アクセスが拒否されました。

<AccordionGroup>
  <Accordion title="AUTHORIZATION">
    **Error Code**: **PLACEHOLDER\_14**\
    **Status Code**: **PLACEHOLDER\_15**

    **Description**: You don't have permission to perform this action.

    **Troubleshooting**:

    1. Verify you have the required role/permissions
    2. Check if you're a member of the project/team
    3. Contact project/team admin to grant access
    4. Ensure you're accessing the correct resource
  </Accordion>

  <Accordion title="PERMISSION_DENIED">
    **Error Code**: **PLACEHOLDER\_16**\
    **Status Code**: **PLACEHOLDER\_17**

    **Description**: Permission denied for the requested operation.

    **Troubleshooting**:

    1. Review your user role and permissions
    2. Check project/team access settings
    3. Verify resource ownership
    4. Contact administrator for access
  </Accordion>

  <Accordion title="DOMAIN_NOT_ALLOWED">
    **Error Code**: **PLACEHOLDER\_18**\
    **Status Code**: **PLACEHOLDER\_19**

    **Description**: Your email domain is not allowed for this operation.

    **Troubleshooting**:

    1. Verify your email domain is whitelisted
    2. Contact administrator to add your domain
    3. Use an allowed email address
  </Accordion>
</AccordionGroup>

### 404 見つかりません

要求されたリソースは存在しません。

<AccordionGroup>
  <Accordion title="ENTITY_NOT_FOUND">
    **Error Code**: **PLACEHOLDER\_20**\
    **Status Code**: **PLACEHOLDER\_21**

    **Description**: The requested resource was not found.

    **Common Scenarios**:

    * Project not found
    * Agent not found
    * Document not found
    * User not found

    **Troubleshooting**:

    1. Verify the resource ID is correct
    2. Check if the resource was deleted
    3. Ensure you have access to the resource
    4. Verify you're using the correct project/workspace
  </Accordion>

  <Accordion title="FILE_NOT_FOUND">
    **Error Code**: **PLACEHOLDER\_22**\
    **Status Code**: **PLACEHOLDER\_23**

    **Description**: The requested file does not exist.

    **Troubleshooting**:

    1. Verify the file ID or path is correct
    2. Check if the file was deleted
    3. Ensure the file is in the expected location
    4. Verify file permissions
  </Accordion>

  <Accordion title="FLOW_NOT_FOUND">
    **Error Code**: **PLACEHOLDER\_24**\
    **Status Code**: **PLACEHOLDER\_25**

    **Description**: The requested workflow/flow was not found.

    **Troubleshooting**:

    1. Verify the flow ID is correct
    2. Check if the flow was deleted
    3. Ensure you have access to the flow
    4. Verify the flow exists in the current project
  </Accordion>

  <Accordion title="CONFIG_NOT_FOUND">
    **Error Code**: **PLACEHOLDER\_26**\
    **Status Code**: **PLACEHOLDER\_27**

    **Description**: Required configuration was not found.

    **Troubleshooting**:

    1. Verify configuration exists
    2. Check configuration setup in settings
    3. Ensure required services are configured
    4. Review configuration documentation
  </Accordion>
</AccordionGroup>

### 500 内部サーバーエラー

調査が必要なサーバー側のエラー。

<AccordionGroup>
  <Accordion title="ENGINE_OPERATION_FAILURE">
    **Error Code**: **PLACEHOLDER\_28**\
    **Status Code**: **PLACEHOLDER\_29**

    **Description**: An internal engine operation failed.

    **Troubleshooting**:

    1. Retry the request after a few moments
    2. Check system status at **PLACEHOLDER\_30**
    3. If persistent, contact support with error details
    4. Provide error ID if available
  </Accordion>

  <Accordion title="EXTERNAL_SERVICE">
    **Error Code**: **PLACEHOLDER\_31**\
    **Status Code**: **PLACEHOLDER\_32**

    **Description**: An external service required for this operation failed.

    **Common Scenarios**:

    * LLM provider API failure
    * Third-party integration failure (Google Drive, Slack, etc.)
    * External API timeout

    **Troubleshooting**:

    1. Check external service status
    2. Verify API keys/credentials for external services
    3. Retry the request
    4. Check integration configuration
    5. Contact support if issue persists
  </Accordion>

  <Accordion title="INFRASTRUCTURE">
    **Error Code**: **PLACEHOLDER\_33**\
    **Status Code**: **PLACEHOLDER\_34**

    **Description**: Infrastructure error (database, storage, etc.).

    **Troubleshooting**:

    1. Retry the request
    2. Check system status
    3. If persistent, contact support
    4. Provide error details and timestamp
  </Accordion>

  <Accordion title="OPEN_AI_FAILED">
    **Error Code**: **PLACEHOLDER\_35**\
    **Status Code**: **PLACEHOLDER\_36**

    **Description**: OpenAI API call failed.

    **Troubleshooting**:

    1. Check OpenAI service status
    2. Verify API key is valid and has credits
    3. Check rate limits
    4. Retry with exponential backoff
    5. Verify model availability
  </Accordion>
</AccordionGroup>

### 503 サービスは利用できません

サービスが一時的に利用できなくなりました。

<AccordionGroup>
  <Accordion title="EXECUTION_TIMEOUT">
    **Error Code**: **PLACEHOLDER\_37**\
    **Status Code**: **PLACEHOLDER\_38**

    **Description**: Operation timed out.

    **Troubleshooting**:

    1. Retry the request
    2. Simplify the operation if possible
    3. Check if system is under heavy load
    4. Break down large operations into smaller ones
    5. Contact support if timeout persists
  </Accordion>
</AccordionGroup>

## ビジネス ロジック エラー

<AccordionGroup>
  <Accordion title="QUOTA_EXCEEDED">
    **Error Code**: **PLACEHOLDER\_39**\
    **Status Code**: **PLACEHOLDER\_40** or **PLACEHOLDER\_41**

    **Description**: You have exceeded your quota limit.

    **Troubleshooting**:

    1. Check your current usage in **My Account** > **Dashboard**
    2. Review subscription limits
    3. Upgrade your plan if needed
    4. Wait for quota reset period
    5. Contact sales for quota increase
  </Accordion>

  <Accordion title="FEATURE_DISABLED">
    **Error Code**: **PLACEHOLDER\_42**\
    **Status Code**: **PLACEHOLDER\_43**

    **Description**: This feature is disabled for your account.

    **Troubleshooting**:

    1. Check your subscription plan
    2. Verify feature availability
    3. Upgrade plan if feature requires higher tier
    4. Contact support for feature access
  </Accordion>

  <Accordion title="FLOW_IN_USE">
    **Error Code**: **PLACEHOLDER\_44**\
    **Status Code**: **PLACEHOLDER\_45**

    **Description**: The workflow is currently in use and cannot be modified.

    **Troubleshooting**:

    1. Wait for active executions to complete
    2. Cancel active workflow runs
    3. Check workflow execution status
    4. Retry after executions complete
  </Accordion>

  <Accordion title="EXISTING_USER">
    **Error Code**: **PLACEHOLDER\_46**\
    **Status Code**: **PLACEHOLDER\_47**

    **Description**: User with this email already exists.

    **Troubleshooting**:

    1. Try logging in instead of signing up
    2. Use password reset if you forgot credentials
    3. Use a different email address
    4. Contact support if account recovery is needed
  </Accordion>
</AccordionGroup>

## 統合固有のエラー

<AccordionGroup>
  <Accordion title="INVALID_APP_CONNECTION">
    **Error Code**: **PLACEHOLDER\_48**\
    **Status Code**: **PLACEHOLDER\_49**

    **Description**: Invalid or expired app connection (OAuth integration).

    **Troubleshooting**:

    1. Re-authenticate the integration
    2. Check OAuth token expiration
    3. Verify integration credentials
    4. Reconnect the integration in settings
  </Accordion>

  <Accordion title="INVALID_SAML_RESPONSE">
    **Error Code**: **PLACEHOLDER\_50**\
    **Status Code**: **PLACEHOLDER\_51**

    **Description**: Invalid SAML response from SSO provider.

    **Troubleshooting**:

    1. Verify SSO configuration
    2. Check SAML metadata URL
    3. Ensure SSO provider is accessible
    4. Contact support for SSO configuration review
  </Accordion>

  <Accordion title="RATE_LIMITED">
    **Error Code**: **PLACEHOLDER\_52** or **PLACEHOLDER\_53**\
    **Status Code**: **PLACEHOLDER\_54**

    **Description**: API rate limit exceeded.

    **Troubleshooting**:

    1. Wait for rate limit window to reset
    2. Implement exponential backoff
    3. Reduce request frequency
    4. Check rate limit headers in response
    5. Upgrade plan for higher rate limits
  </Accordion>
</AccordionGroup>

## 助けを求める

ここに記載されていないエラーが発生した場合、またはサポートが必要な場合は、次の手順を実行してください。

1. **エラーの詳細を確認**: エラー コード、メッセージ、および error\_id をメモします。
2. **システム ステータスを確認**: 既知の問題については、`status.getodin.ai` にアクセスしてください。
3. **ドキュメントの確認**: 関連する API ドキュメントを確認します。
4. **サポートに連絡**: [Support](support@automationanywhere.com) に次の内容を電子メールで送信します。
   * エラーコードとメッセージ
   * エラー ID (利用可能な場合)
   * 再現手順
   * リクエスト/レスポンスの詳細 (サニタイズ済み)
   * エラーのタイムスタンプ