> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zeotap.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Resolve Journey Errors

> A technical reference for understanding and resolving Journey execution failures. When a profile reaches a destination node but fails to deliver, the system generates a Failure Status Code. This guide helps you identify, diagnose, and fix those failures.

## 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](/articles/orchestrate-customer/journey-error-codes).

| Error Code             | Category    | Severity | Technical Definition                                        |
| ---------------------- | ----------- | -------- | ----------------------------------------------------------- |
| `CONSENT_NOT_PROVIDED` | Policy      | Info     | Profile suppressed based on privacy/policy flags.           |
| `EVENT_PARSING_FAILED` | Data        | Error    | Error in the liquid syntax or data transformation logic.    |
| `BAD_REQUEST`          | Data        | Error    | Destination rejected the payload (missing required fields). |
| `AUTHENTICATION_ERROR` | Auth        | Critical | Destination credentials/API keys have expired.              |
| `RATE_LIMIT`           | Throttle    | Warning  | Destination API rate limits exceeded.                       |
| `SERVER_ERROR`         | Destination | Error    | Internal failure on the destination platform.               |
| `SERVICE_UNAVAILABLE`  | Destination | Warning  | Destination service temporarily unavailable.                |
| `ENDPOINT_NOT_FOUND`   | Config      | Critical | Destination endpoint URL does not exist.                    |
| `MISC_ERROR`           | Unknown     | Error    | Uncategorized or non-standard API response.                 |

## Severity Level Guide

| Level        | When It Occurs                     | Recommended Response                                                                                          |
| ------------ | ---------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| **Critical** | Authentication or endpoint failure | Immediate action required. Delivery has stopped completely. Fix the underlying configuration before retrying. |
| **Error**    | Data or server-side issues         | Investigate root cause. Events are failing but the integration may still be partially functional.             |
| **Warning**  | Rate limits or temporary downtime  | Monitor closely. Events may self-recover with retry logic. No immediate reconfiguration needed.               |
| **Info**     | Policy-driven discards             | Informational. No action needed unless consent or policy configurations need review.                          |

## Related Topics

* To learn how to identify errors visually in the Journey Canvas, refer to [Identify Journey Errors](/articles/orchestrate-customer/identify-journey-errors).
* For detailed resolution steps for each error code, refer to [Journey Error Codes](/articles/orchestrate-customer/journey-error-codes).
* For common troubleshooting workflows and tips, refer to [Troubleshooting Workflows](/articles/orchestrate-customer/journey-troubleshooting).