When a document processing request fails, OSS returns an XML error response containing an error code and details to help you identify and fix the issue.
Error response structure
The following is an example error response:
<Error>
<Code>Imm Client</Code>
<Message>InvalidArgument, [target]:is required. 9D31D05E-FC1C-582E-B31E-3E1327F97B53</Message>
<RequestId>647EB6AC7B423D3538DB6D61</RequestId>
<HostId>userdomain</HostId>
</Error>The response includes the following fields:
| Field | Description |
|---|---|
Code | The error code returned for the document processing request. |
Message | Details about the error. Format: IMM error info, [IMM request ID] (optional). |
RequestId | The unique UUID identifying the failed request. Provide this ID when contacting technical support for cause analysis. |
HostId | The endpoint of the bucket where the documents to be processed are stored. |
Error codes
| Error code | Description | Solution |
|---|---|---|
Imm Client | An error occurred during document processing. | Verify that the document processing parameters you configure are valid. For parameter details, see Document processing. |
What's next
For errors returned by Intelligent Media Management (IMM) outside of the OSS document processing context, see Error handling.
该文章对您有帮助吗？