Skip to main content

Overview

When a profile reaches a destination node in a Journey but fails to deliver, the system generates a Failure Status Code. Understanding these codes allows you to distinguish between configuration errors and external service disruptions. This guide is intended for developers, integration engineers, and client-side technical teams who are instrumenting, debugging, or monitoring Journey-based workflows.

Error Reference Matrix

Use this table as a quick-reference lookup. For detailed resolution steps, see Journey Error Codes.
Error CodeCategorySeverityTechnical Definition
CONSENT_NOT_PROVIDEDPolicyInfoProfile suppressed based on privacy/policy flags.
EVENT_PARSING_FAILEDDataErrorError in the liquid syntax or data transformation logic.
BAD_REQUESTDataErrorDestination rejected the payload (missing required fields).
AUTHENTICATION_ERRORAuthCriticalDestination credentials/API keys have expired.
RATE_LIMITThrottleWarningDestination API rate limits exceeded.
SERVER_ERRORDestinationErrorInternal failure on the destination platform.
SERVICE_UNAVAILABLEDestinationWarningDestination service temporarily unavailable.
ENDPOINT_NOT_FOUNDConfigCriticalDestination endpoint URL does not exist.
MISC_ERRORUnknownErrorUncategorized or non-standard API response.

Severity Level Guide

LevelWhen It OccursRecommended Response
CriticalAuthentication or endpoint failureImmediate action required. Delivery has stopped completely. Fix the underlying configuration before retrying.
ErrorData or server-side issuesInvestigate root cause. Events are failing but the integration may still be partially functional.
WarningRate limits or temporary downtimeMonitor closely. Events may self-recover with retry logic. No immediate reconfiguration needed.
InfoPolicy-driven discardsInformational. No action needed unless consent or policy configurations need review.
Last modified on March 21, 2026