%s in error messages are placeholders used to indicate where a specific value, such as an Order ID or an item name, will be inserted when the actual error message is displayed.
| Category | Error Code | Message | How to resolve |
|---|---|---|---|
| API (Client-Side) | SERVICE-4002 | Invalid values specified for %s. | The SERVICE-4002 error indicates that one or more of the values you provided in your request are not acceptable. To resolve this error, update the invalid values specified in the error message and retry the request. |
| API (Client-Side) | SERVICE-4003 | Mandatory parameters: %s is/are missing. | If you’re using fabric APIs, your request needs specific required headers and sometimes parameters. If any of these are missing, you’ll get a service error that tells you exactly what’s needed. |
| API (Client-Side) | SERVICE-4004 | Specified %s doesn’t exist. | This error occurs when a specified parameter such as an Order ID, Allocation ID, or Payment ID doesn’t exist.
|
| API (Client-Side) | SERVICE-4005 | Specified %s already created/creation is in-progress. | This error occurs when records are still being processed by fabric. The time to process records can take up to 20 minutes depending on the number of records being processed. Please wait a few minutes and try again. |
| API (Client-Side) | SERVICE-4006 | This record has been modified by another request… | This error can occur when multiple requests try to modify the same record at the same time. It is recommended that you set up a retry mechanism in your code. This error is often resolved by re-submitting a request. If the error persists, contact fabric support. |
| API (Client-Side) | SERVICE-4007 | Multiple fields are invalid/missing. | This error means there are several issues with your request’s fields. For instance, your order number might be null, or a required item could be missing from the payload. The error message will tell you exactly what’s wrong. Once you add or correct the missing fields, the error will resolve. |
| Service (Server-Side) | SERVICE-3000 | Downstream service error: %s. | Sometimes, errors originate from fabric integrations with payment systems or other external services. When this happens, fabric can tell you which service caused the problem, but to resolve it, you’ll need to check the logs for that specific integration. For example, if it’s a payment issue, you’d look at your payment integration logs. |
| Service (Server-Side) | SERVICE-3001 | Resource creation/update error: %s. | This error means there was a problem when trying to create or update a resource. The %s in the message will typically be replaced by more specific details about why the creation or update failed. |
| Service (Server-Side) | SERVICE-5000 | Internal service error. | This error means something went wrong on our end. Please check for any service disruptions with fabric or other connected downstream services you rely on. |
| Service (Server-Side) | SERVICE-5001 | Service timeout: %s. | A service timeout happens after 20 seconds. If a timeout occurs, retry the request. If a timeout continues to happen, contact fabric support. |
Example service errors
SERVICE-4003 Error
SERVICE-4003 Error
{
"type": "CLIENT_ERROR",
"errorCode": "SERVICE-4003",
"message": "Mandatory param(s): `Header: X-Fabric-Channel-Id` is/are missing",
"errors": [],
"context": {
"service": "orders",
"endpoint": "POST /v3/orders"
}
}
SERVICE-4004 Error
SERVICE-4004 Error
{
"type": "CLIENT_ERROR",
"errorCode": "SERVICE-4004",
"message": "Specified `OrderId: 44354534543` doesn't exist",
"context": {
"service": "orders",
"endpoint": "GET /v3/orders/44354534543"
}
}
SERVICE-4005 Error
SERVICE-4005 Error
{
"type": "CLIENT_ERROR",
"errorCode": "SERVICE-4005",
"message": "Specified `orderNumber: oms_1750783753456` already created/creation is in-progress",
"context": {
"service": "orders",
"endpoint": "POST /v3/orders"
}
}
SERVICE-4006 Error
SERVICE-4006 Error
{
"type": "CLIENT_ERROR",
"errorCode": "SERVICE-4006",
"message": "This record has been modified by another request, please resubmit.",
"context": {
"service": "allocations",
"endpoint": "PUT /v3/allocations/allocation-request-id/1000667280"
}
}
SERVICE-4007 Error
SERVICE-4007 Error
{
"type": "CLIENT_ERROR",
"errorCode": "SERVICE-4007",
"message": "Multiple field(s) are invalid/missing",
"errors": [
{
"type": "CLIENT_ERROR",
"errorCode": "SERVICE-4000",
"message": "items must be added to the request payload!"
},
{
"type": "CLIENT_ERROR",
"errorCode": "SERVICE-4000",
"message": "'orderNumber' can't be null"
}
],
"context": {
"service": "orders",
"endpoint": "POST /v3/orders"
}
}