---
title: "abandon_request"
description: "Fix code: abandon_request"
canonical: "https://studio.inttegro.dev/e/f-abandon_request"
format: inttegro-machine-docs/v1
language: "PHP"
sdk_version: "v14.1.1"
reader_profile: optional
reader_manifest: "https://studio.inttegro.dev/machine/php/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: 328
model_token_report: "https://studio.inttegro.dev/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: []
estimated_tokens: 1005
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Fix code: abandon_request This PHP representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

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

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 [unknown_error](https://studio.inttegro.dev/machine/php/e/t-unknown_error.md) when those concerns enter scope.

## Document content

# abandon\_request

Fix code indicating the request cannot succeed and should be abandoned entirely.

## What this means

The Inttegro API has determined that your requested operation is fundamentally impossible given the current system state or immutable business rules, and no amount of retrying, parameter modification, or waiting will make it succeed. This fix code appears when you're attempting something that violates core constraints of the platform—for example, trying to cancel an order when that order has already been completed and reached a terminal state, or attempting to modify a payment that has already been captured and is now immutable for compliance and auditing reasons. Unlike `change_request_parameters` where correcting values enables success, or `satisfy_precondition` where completing prerequisites allows progress, `abandon_request` signals that the operation you're attempting is categorically impossible.

When you encounter this fix code, examine your application logic to understand why you're attempting an invalid operation—you may have incorrect assumptions about object states, or you might need to redesign your workflow to account for the constraints the Inttegro API enforces. The appropriate response is to stop retrying this specific request and either accept that the operation cannot be performed or find an alternative approach to achieve your business objective.

## Example error response

```json
{
  "error": {
    "type": "invalid_request_parameter",
    "cause": "precondition_unmet",
    "code": "1812",
    "message": "operation not allowed",
    "detail": "Cannot cancel order `or_abc123` because it has already been completed. Orders in terminal states cannot be modified.",
    "fix_code": "abandon_request",
    "url": "https://studio.inttegro.com/e/1812"
  }
}
```

## Related errors

- [unknown\_error](https://studio.inttegro.dev/machine/php/e/t-unknown_error.md) - May result in abandon fix code