input stringlengths 13 31 | label stringclasses 2
values | note stringlengths 70 169 |
|---|---|---|
HTTP 500 Internal Server Error | retryable | Generic server-side issue, often transient. Retrying might resolve it. |
HTTP 503 Service Unavailable | retryable | Server is temporarily unable to handle the request due to overloading or maintenance. Retry after a delay. |
HTTP 429 Too Many Requests | retryable | Rate limit exceeded. Client should wait and retry with exponential backoff. |
HTTP 408 Request Timeout | retryable | The server did not receive a complete request message within the time it was prepared to wait. Could be network or server load. |
HTTP 502 Bad Gateway | retryable | Server acting as a gateway received an invalid response from an upstream server. Often transient. |
HTTP 504 Gateway Timeout | retryable | Gateway or proxy timed out waiting for a response from an upstream server. Often transient. |
Network connection refused | retryable | The client failed to establish a connection to the server. Can be transient due to network issues or server restart. |
DNS resolution failed | retryable | The domain name could not be resolved to an IP address. Often a transient network or DNS server issue. |
Database connection error | retryable | A temporary issue connecting to the database, possibly due to overload or transient network problems. Retrying might succeed. |
HTTP 409 Conflict | retryable | The request could not be completed due to a conflict with the current state of the resource. If the conflict is resolvable by a state change, retrying might work. |
HTTP 400 Bad Request | permanent | The server cannot process the request due to a client error (e.g., malformed syntax, invalid request message framing). Requires client-side fix. |
HTTP 401 Unauthorized | permanent | Authentication credentials are missing or invalid. Client needs to provide valid credentials. |
HTTP 403 Forbidden | permanent | The client does not have permission to access the resource. Even with authentication, access is denied. |
HTTP 404 Not Found | permanent | The requested resource could not be found on the server. The URL is likely incorrect or the resource doesn't exist. |
HTTP 405 Method Not Allowed | permanent | The HTTP method used (e.g., PUT, DELETE) is not supported for the requested resource. Client needs to use a different method. |
HTTP 410 Gone | permanent | The requested resource is no longer available at the server and no forwarding address is known. It should be considered permanently unavailable. |
HTTP 413 Payload Too Large | permanent | The request entity is larger than limits defined by the server. Client needs to reduce the payload size. |
HTTP 415 Unsupported Media Type | permanent | The server refuses to accept the request because the payload format is in an unsupported format. Client needs to use a supported content type. |
HTTP 422 Unprocessable Entity | permanent | The server understands the content type of the request entity, but was unable to process the contained instructions due to semantic errors. Client needs to correct data. |
HTTP 501 Not Implemented | permanent | The server does not support the functionality required to fulfill the request. This is usually a permanent server limitation. |
Invalid API Key | permanent | The provided API key is incorrect or expired. Client must update their authentication credentials. |
Missing required parameter | permanent | A mandatory parameter or field was omitted from the request. Client needs to include all required parameters. |
Resource already exists | permanent | The client attempted to create a resource that already exists and cannot be overwritten or updated by this specific request. Client logic needs adjustment. |
Transaction deadlock detected | retryable | A database transaction could not complete due to a deadlock. Retrying the transaction often resolves this. |
Service unavailable (non-HTTP) | retryable | A generic indication that the service is temporarily unable to handle the request, similar to HTTP 503 but for non-HTTP APIs. |
YAML Metadata Warning:empty or missing yaml metadata in repo card
Check out the documentation for more information.
API Error Retryability Classification
This dataset classifies common API error messages and HTTP status codes into 'retryable' or 'permanent' categories. It helps developers implement robust error handling strategies, distinguishing between transient issues that warrant retries and fundamental problems requiring immediate client-side correction.
25 rows · category: reliability · licence: CC0-1.0 (public domain)
Usage
import api_error_retryability_classifier as classifier
# To make this example runnable, create a data.jsonl file
# in the same directory as api_error_retryability_classifier.py
# with content like:
# {"input": "HTTP 500 Internal Server Error", "label": "retryable", "note": "..."}
# {"input": "HTTP 404 Not Found", "label": "permanent", "note": "..."}
# Load all classification data
all_errors = classifier.load()
print(f"Total error classifications loaded: {len(all_errors)}")
# Get classification for a specific error
classification_500 = classifier.get_classification("HTTP 500 Internal Server Error")
print(f"HTTP 500 is: {classification_500}") # Expected: retryable
# Check if an error is retryable
is_429_retryable = classifier.is_retryable("HTTP 429 Too Many Requests")
print(f"Is HTTP 429 retryable? {is_429_retryable}") # Expected: True
is_404_retryable = classifier.is_retryable("HTTP 404 Not Found")
print(f"Is HTTP 404 retryable? {is_404_retryable}") # Expected: False
Sample rows
{"input": "HTTP 500 Internal Server Error", "label": "retryable", "note": "Generic server-side issue, often transient. Retrying might resolve it."}
{"input": "HTTP 503 Service Unavailable", "label": "retryable", "note": "Server is temporarily unable to handle the request due to overloading or maintenance. Retry after a delay."}
{"input": "HTTP 429 Too Many Requests", "label": "retryable", "note": "Rate limit exceeded. Client should wait and retry with exponential backoff."}
Files
| File | What |
|---|---|
data.jsonl |
the dataset, one JSON object per line |
tool.py |
stdlib-only loader and helpers |
test_tool.py |
tests that pass against the data |
Source: https://github.com/simalidudu-boop/api-error-retry-classification
Support
This is free and public domain. If it saved you time, zap it: SharkSkin@coinos.io
Generated and maintained by an autonomous pipeline. Issues and PRs welcome.
- Downloads last month
- -