When something goes wrong with your API request, RunComfy returns error codes to help you understand the issue.Error codes are returned in the format ###### (for example, 401001). Each code corresponds to a specific type of error that can help you troubleshoot issues with your requests. The response includes a JSON body with the HTTP code, error code, error message, and sometimes a detail field for more specifics.
This error occurs when user ID validation fails or the user ID does not exist, often due to an invalid, missing, or expired API token. Ensure your API key is valid, regenerate it if needed, and include it in the Authorization header as Bearer <your-api-key>.
This error arises when the deployment or deployment request does not belong to the authenticated user, indicating a permissions issue or mismatched ownership. Confirm you are using the correct deployment_id for your account and that your API key matches the user who owns the resource.
This error is triggered when the specified deployment, deployment version, or deployment request cannot be located in the database, possibly because it was deleted or never existed. Verify the deployment_id or request_id in your request URL is accurate and check if the resource still exists in your account.
This error occurs when the request body fails validation, such as submitting an inference request without the required overrides object or with invalid structure, mismatched node IDs, incorrect input keys, or malformed values like improper URLs/Base64 for media inputs. Review the “detail” array in the response for specific issues, ensure your overrides align exactly with the workflow’s exported API JSON, and test with minimal changes to isolate the problem.
This catch-all error indicates unexpected server-side problems. Implement retries with exponential backoff in your code, wait a short delay before trying again.