Bring Your Own Node Service Errors

The Bring Your Own Node (BYON) service runs custom code nodes within Agentforce agent workflows. When your agent runs, the reasoning engine walks a graph of steps to fulfill a request. Each node in that graph represents a discrete operation. The reasoning engine determines which node to call, assembles the inputs, and calls your code to execute it. Errors from this service typically indicate that the requested node wasn’t found, that the request payload failed validation, that the caller lacked permission to execute the node, or that the execution timed out or was cancelled before completing.

The code identifier you specified in the request doesn’t match any registered node in this service instance. No execution was attempted. Retrying won’t help until the identifier is corrected or the node is registered.

This error occurs when:

• The code_id value contains a typo or uses incorrect casing.
• The node was registered under a different identifier than the one in your request.
• The node hasn’t been registered yet, or the registration didn’t complete successfully.
• The request is targeting the wrong environment (for example, staging instead of production).

To resolve this error:

1. Verify the code_id value exactly matches the identifier used when the node was registered. The value is case-sensitive.
2. Confirm the node is registered in the environment your request is targeting.
3. Confirm the registration completed successfully before retrying.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: ICR_BYON_CODE_NOT_FOUND
• The exact code_id value you used in your request

The node execution was cancelled before it could complete. This is usually a temporary issue. Retrying typically succeeds.

This error occurs when:

• The network connection between the caller and the service was interrupted mid-request.
• The service was restarting or scaling at the time of the request.
• The caller closed the connection before execution finished.

To resolve this error:

1. Wait 5 seconds and try again. Cancellation errors are almost always temporary.
2. If cancellations happen consistently, verify that your network connection to the service endpoint is stable.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: ICR_BYON_EXECUTION_CANCELLED
• The code_id that was being executed, and whether cancellations happen on every request or only occasionally

The node determined that the caller doesn’t have permission to run this execution. The request was received but access was denied before execution could begin. Retrying won’t help until the permissions issue is resolved.

This error occurs when:

• The caller’s credentials don’t satisfy the access requirements for this node.
• The account or service principal hasn’t been granted the necessary permissions.
• The caller is attempting to access a resource or capability restricted to specific users or roles.

To resolve this error:

1. Verify that the credentials in your request are current and haven’t expired.
2. Confirm that the account or service principal you’re using has been granted the necessary permissions for this node.
3. If you recently changed roles or credential configurations, confirm those changes have propagated.
4. Contact your Salesforce admin to confirm your account is authorized to call this node.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: ICR_BYON_EXECUTION_FORBIDDEN
• The code_id you were attempting to execute, and the identity or role your request was made under (don’t include credentials or tokens)

The node execution didn’t complete within the allowed time limit and was stopped automatically. This is usually a temporary issue. Waiting a few seconds and trying again may succeed.

This error occurs when:

• The node performs a long-running operation, such as calling an external service or processing a large payload, that occasionally exceeds its time budget.
• A downstream system the node depends on was slow to respond.
• The service experienced a cold start or elevated load at the time of the request.

To resolve this error:

1. Wait 5 seconds and try again. Most timeout errors are temporary.
2. If timeouts occur consistently for a specific operation, check whether the node makes calls to external services that may be slow or unavailable.
3. If you control the node code, consider breaking large operations into smaller steps or adding early exits for cases that can’t complete in time.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: ICR_BYON_EXECUTION_TIMEOUT
• The code_id that was being executed, and a description of what the node was doing when the timeout occurred

The request payload failed validation and execution wasn’t started. The service received the request but couldn’t process it because the content was malformed, missing required fields, or contained values of the wrong type. Retrying with the same payload won’t help.

This error occurs when:

• A required field in the request payload was missing or empty.
• The payload contained a value of the wrong type (for example, a number where a string was expected).
• The payload wasn’t valid JSON or was corrupted in transit.
• The request was built against an older version of the node interface that no longer matches the current expected format.

To resolve this error:

1. Review the request payload and verify all required fields are present and correctly typed.
2. Confirm the payload is valid JSON and wasn’t modified or corrupted between your application and the service.
3. Check the node interface specification for the code_id you’re calling to confirm your request format matches what’s expected.
4. If you recently updated your client or the node interface, verify the two are compatible.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: ICR_BYON_INVALID_REQUEST
• The code_id that was being called, and a sanitized example of the request payload (remove any sensitive values)

An unexpected error occurred while the node was executing and the execution couldn’t complete. This indicates an unhandled exception or error condition in the node code itself. Retrying won’t help until the underlying issue in the code is resolved.

This error occurs when:

• The node raised an unhandled exception during execution.
• The node encountered an unexpected input value that caused a runtime error.
• A dependency the node relies on behaved in an unexpected way.

To resolve this error:

1. Review the node code associated with the code_id for bugs or edge cases that might cause a crash on the specific input you sent.
2. Check whether the request payload contains unusual or edge-case values the node may not handle correctly.
3. If you recently updated the node, compare it to the previous version to identify what changed.

If the issue persists, contact Salesforce Customer Support with the following information.

• The trace ID from the error response (instance field, format urn:trace:...)
• The error code: ICR_BYON_NODE_FAILURE
• The code_id that was being executed, and a description of the input that triggered the error (omit any sensitive data)

j

Get Started

Agentforce Examples

Agent Script

Agentforce DX

Agentforce APIs and SDKs

Agentforce Actions

Agentforce Service Errors

Agent Service Reasoner Errors

Agentforce Data Library Errors

Authentication Service Errors

Bring Your Own Node Service Errors

General Agentforce Service Errors

Interactive Data Science Service Errors

Language Detection Service Errors

ML Lake Service Errors

Model Builder Errors

Prediction Service Errors

Models and Prompts

Headless Agentforce Development