Error codes and what they mean

Use this page to understand what the message means and what to do next.

If your error is not listed here, check I received an alert — what now? for general guidance, or contact HC with the event ID and the full error text.

Validation errors

The event data does not meet the requirements of the destination system.

• Missing required field — a field that the destination system requires was not present in the source data. The error message names the field. If the value can be added (e.g. a phone number that exists in the source system but was not included), fix it in the Control Panel and resend. If the value is genuinely not available in the source data, contact HC — a configuration change may be needed.

• Invalid value — a field contains a value the destination system does not accept. Common examples: an unrecognised currency code, a tax code that does not exist in the ERP, a text value in a numeric field, or a string that exceeds the maximum field length. Correct the value and resend if you can, or contact HC if the issue is in the mapping logic.

• Duplicate record — an event with the same reference has already been processed. Check whether the record exists in the destination. If it does, no action is needed. If it does not, contact HC.

• Record not found — the event references a record in the destination that does not exist (e.g. a return for an order that HC did not create in the ERP, or a customer record that is missing). Contact HC.

Connection errors

HC could not reach the destination system.

• Timeout — the destination system did not respond within the expected time limit. HC will retry automatically. If timeouts are recurring or the destination is consistently slow, contact HC.

• Authentication error — HC's connection to the destination system has expired or been revoked. This typically means the API credentials need to be refreshed. Contact HC immediately — this error will affect all events on the stream until resolved.

• Rate limit — the destination system rejected the request because too many API calls were made in a short period. HC retries automatically with backoff. If rate limiting persists across a long period, contact HC.

• Destination unavailable — the destination system returned an error indicating it is down or unreachable. HC retries automatically. If the destination is back online and events are still failing, contact HC.

Business rule errors

The destination system rejected the event because it violated an internal validation rule. These errors are specific to your destination system's configuration and cannot be resolved from the Control Panel. Contact HC with the event ID and the full error message.