Resolutions By Error Code

• 0000 - Unhandled General

  • Poor error handling implementation in a custom node or misconfiguration in a core node.

    • Check the error message for more details.

    • If it's from a custom node, ensure your code is properly wrapped in a try...catch block and all possible exceptions are handled.

    • If it's from a core node, ensure it's configured correctly.

• 1000 - Configuration General

  • One or more properties on a node are misconfigured.

    • Check the node configuration screen and ensure all properties are set up correctly.

• 1010 - Configuration Missing

  • This error usually means a node is missing some configuration.

    • Check the node configuration screen and ensure all required properties have been configured.

• 1020 - Configuration Invalid

  • A configuration property is set, but its value is invalid.

    • Check the node configuration screen and ensure all required properties have been configured with the correct values.

• 2000 - Security General

  • An umbrella error for security issues.

    • May require deeper investigation into log files.

• 2010 - Security Auth

  • Authentication with the orchestration layer failed.

    • Ensure that your payload contains an API key, and that the API key is valid.

• 3000 - Input General

  • A general error for when something is wrong with the message or message payload.

    • Inspect the error message and adjust the payload input accordingly.

• 3011 - Input Data Missing

  • A value that is expected by the orchestration layer is not present on the message or message payload.

    • Ensure that all required values are present on the message payload.

• 3012 - Input Data Malformed

  • A property on the message payload is not in the expected format or is an invalid type.

    • Ensure that all required values on the message payload are in the correct format.

• 4000 - Transport General

  • A general error for when something went wrong with the transport layer between a node and a remote endpoint.

    • Inspect the error message and adjust configuration or input values accordingly.

• 4010 - Transport Remote HTTP

  • An HTTP error occurred while a node attempted communication with a remote endpoint.

    • Ensure that the node has been configured correctly and is providing all of the correct information that the remote endpoint requires.

    • If everything appears in order with the node, investigation into the API responsible for the remote endpoint may be required.

• 4011 - Transport Timeout

  • An HTTP request made from a node to a remote endpoint took too long to return a response.

    • Inspect the data that is being provided and ensure it is correct.

    • Ensure that the remote API is healthy.

    • Adjust timeout values if available.

• 4012 - Transport Auth

  • Authentication failed between a node and a remote endpoint.

    • Ensure that all credentials and API keys are set correctly in the context of the node where the HTTP request is failing.

• 4020 - Transport Network

  • A network-related error occurred while a node attempted to access a remote endpoint.

    • Ensure that the orchestration layer is able to make outbound requests.

    • Ensure healthy connectivity in the orchestration environment.

    • Ensure that the remote API is accessible.

• 4030 - Transport Bad Response

  • A request made to a remote endpoint by the relevant node returned an unexpected or malformed response.

    • Ensure that all component versions are in order.

    • Ensure that the node is configured correctly.

    • Ensure that the remote API configured correctly.

• 5000 - Server General

  • A general server-related error occurred in the orchestration layer.

    • Inspect the error message and adjust configuration or input accordingly.

• 5011 - Server Data Missing

  • The orchestration layer attempted to access a value that is not available. This can occur while trying to access the flow or global context.

    • Inspect your configuration and find values that may be attempting to access a flow or global context value.

    • Ensure that the corresponding value has been set in the flow or global context as applicable.

• 5012 - Server Data Malformed

  • The orchestration layer attempted to access a value that is invalid or malformed. This can occur while trying to access the flow or global context.

    • Inspect your configuration and find values that may be attempting to access a flow or global context value.

    • Ensure that the corresponding value has been set with the expected value or format in the flow or global context as applicable.