When a file processing request fails, OSS returns an XML error response containing an error code and message. Use these fields to detect errors programmatically and guide users through resolution.
Error response format
The following example shows a typical error response:
<Error>
<Code>Imm Client</Code>
<Message>InvalidArgument, The parameter OctreeOption is required but not provided.</Message>
<RequestId>647EB6AC7B423D3538DB6C61</RequestId>
<HostId>userdomain</HostId>
</Error>The response contains the following fields:
| Field | Type | Description |
|---|---|---|
Code | String | The error code. Use this field in your application logic to detect and handle errors by type. |
Message | String | A human-readable description of the error, intended for display or logging. Format: IMM error code, IMM error info, [IMM request ID] (optional). |
RequestId | String | The unique ID identifying the failed request, which is required for cause analysis when you contact technical support. |
HostId | String | The endpoint of the bucket where the files to be processed are stored. |
Error codes
| Error code | Description | Solution |
|---|---|---|
Imm Client | An error occurred during file processing. | Check your request parameters. For details, see Processing Parameters. |
What's next
For errors returned directly by Intelligent Media Management (IMM), see Error handling.
该文章对您有帮助吗？