runninghub-api
    runninghub-api
    • Instructions for Use
    • About nodeInfoList
    • About Enterprise ComfyUI API
    • Native ComfyUI API Integration Guide
    • API Error Code Reference
    • Start ComfyUI Task 1 - Basic
      POST
    • Start ComfyUI Task 2 - Advanced
      POST
    • Start AI App Task
      POST
    • Get Workflow JSON
      POST
    • Check Task Status
      POST
    • Check Task Output
      POST
    • Cancel ComfyUI Task
      POST
    • Get Account Information
      POST
    • Upload Resource(image\video\audio)
      POST
    • Upload Lora
      POST
    • Get Webhook Event Details
      POST
    • Resend Specific Webhook Event
      POST

    API Error Code Reference

    API Error Code Reference#

    This document lists all possible error codes returned by the current SDK / REST API, their meanings, common trigger scenarios, and recommended solutions.
    It is intended to help developers quickly locate the cause of an error during integration and troubleshooting.

    Overview#

    CodeIdentifierBrief Description
    301PARAMS_INVALIDInvalid or missing parameters
    380WORKFLOW_NOT_EXISTSThe specified workflow does not exist
    415TASK_INSTANCE_MAXEDNo available dedicated instances
    421TASK_QUEUE_MAXEDConcurrency limit reached for shared API
    423TASK_NOT_FOUNEDTask not found
    433VALIDATE_PROMPT_FAILEDWorkflow validation failed
    801APIKEY_UNSUPPORTED_FREE_USERFree users are not allowed to use API Keys
    802APIKEY_UNAUTHORIZEDAPI Key is unauthorized or expired
    803APIKEY_INVALID_NODE_INFOnodeInfoList does not match the workflow
    804APIKEY_TASK_IS_RUNNINGTask is still running
    805APIKEY_TASK_STATUS_ERRORTask status is abnormal
    806APIKEY_USER_NOT_FOUNDUser not found
    807APIKEY_TASK_NOT_FOUNDTask not found
    808APIKEY_UPLOAD_FAILEDFile upload failed
    809APIKEY_FILE_SIZE_EXCEEDEDFile size exceeds limit
    811CORPAPIKEY_INVALIDEnterprise API Key is invalid
    812CORPAPIKEY_INSUFFICIENT_FUNDSEnterprise account balance is insufficient
    813APIKEY_TASK_IS_QUEUEDTask is queued
    901WEBAPP_NOT_EXISTSWebApp does not exist
    500UNKNOWN_ERRORUnknown error

    Key Error Codes#

    301 PARAMS_INVALID#

    Meaning: The request contains illegal or missing parameters.
    Common causes
    Required fields are empty or in the wrong format
    Parameter types do not match the API specification
    How to fix
    1.
    Compare each field with the latest API documentation (name, type, range).
    2.
    Start with the official minimal sample request, confirm it works, then replace fields with your own data.

    415 TASK_INSTANCE_MAXED#

    Meaning: No available dedicated instances (machines).
    Typical scenarios
    System upgrade or automatic recovery in progress
    Your concurrent tasks have exhausted all dedicated capacity
    How to fix
    1.
    Retry after 30 – 120 seconds.
    2.
    If the error persists, contact technical support to check resource status.

    421 TASK_QUEUE_MAXED#

    Meaning: Your concurrency quota for the shared API is full.
    Impact: New tasks are rejected.
    How to fix
    1.
    Implement client-side queuing and wait until running tasks complete.
    2.
    If you need higher concurrency, contact us to increase your quota.

    433 VALIDATE_PROMPT_FAILED#

    Meaning: Workflow validation failed (includes prompt and node configuration checks).
    Common causes
    Input/output links between nodes violate rules
    Missing or malformed fields
    How to fix
    1.
    Locate the problematic node and field from the msg field in the response.
    2.
    Correct the workflow parameters and resend the request.

    803 APIKEY_INVALID_NODE_INFO#

    Meaning: The supplied nodeInfoList does not match the bound workflow.
    Checklist
    Does each nodeId exist in the workflow definition?
    Do fieldName and fieldValue exactly match the node’s input fields?
    How to fix
    1.
    Retrieve or confirm the latest workflow node information.
    2.
    Ensure every node field name and type matches, then retry the request.

    500 UNKNOWN_ERROR#

    Meaning: An exception not captured by other error codes.
    Typical causes
    Malformed request body (JSON typos, escaping issues, etc.)
    Transient internal service failure
    How to fix
    1.
    First verify that the official sample request works.
    2.
    If the sample succeeds but your request always returns 500, save full request/response logs and contact us for investigation.

    Additional Notes#

    For “not found” errors such as 380 / 901
    Verify the resource ID is correct.
    For “task running / queued” errors such as 804 / 813
    Do not create the task again; query the task status API or wait for a webhook callback.
    For enterprise API Key errors (811 / 812)
    Check whether the key is expired and whether the balance is sufficient.

    Contact Us#

    If you need higher concurrency, assistance with persistent 5xx errors, or any other technical support, please reach out through the official discord channel and provide:
    Request time and taskId
    Full request payload
    Error code and returned message
    We will respond as soon as possible.
    Modified at 2025-06-23 15:46:05
    Previous
    Native ComfyUI API Integration Guide
    Next
    Start ComfyUI Task 1 - Basic
    Built with