Skip to main content

​
Overview

When a Journey execution fails at a destination node, the system assigns a Failure Status Code. Each code categorizes the failure type and indicates whether it requires manual intervention or will auto-resolve with retries.
View Executions panel showing total events, successful events, and failed events count

​
Quick Reference

Error CodeTypeAuto-Retry?First Action
CONSENT_NOT_PROVIDEDPersistentNoCheck user consent attributes and destination mapping
EVENT_PARSING_FAILEDPersistentNoReview data transformation rules and field mappings
BAD_REQUESTPersistentNoValidate required fields and payload format
AUTHENTICATION_ERRORPersistentNoRefresh OAuth token or update API credentials
RATE_LIMITTransientYesReduce batch size or add wait nodes
SERVER_ERRORTransientYesWait and monitor — retries automatically
SERVICE_UNAVAILABLETransientYesCheck destination status page for outages
ENDPOINT_NOT_FOUNDPersistentNoVerify destination endpoint URL configuration
MISC_ERRORVariesNoReview raw error response and contact support
Transient errors (SERVER_ERROR, SERVICE_UNAVAILABLE, RATE_LIMIT) often resolve on their own with automatic retries. Persistent errors (CONSENT_NOT_PROVIDED, BAD_REQUEST, AUTHENTICATION_ERROR, ENDPOINT_NOT_FOUND) require manual intervention to fix the underlying configuration issue.

​
Where Error Codes Appear

Error codes are displayed on the Journey canvas at the node level. Destination nodes with failures show red error count badges, while successful deliveries show green indicators. Click on any node to view the execution detail panel with the specific error code and affected record count.
Workflow canvas showing Send to Destination nodes with success/error count indicators
FieldDetail
CategoryPolicy
SeverityInfo
DefinitionUser has not provided the required consent or consent status is classified as not provided.
Action TypeValidation
What it Means: The user or event was blocked due to missing or insufficient consent permissions for the target destination. Root Causes:
  • Users have not opted in to the specific communication channel
  • Consent data is missing from the user profile entirely
  • Consent mapping between Zeotap and the destination is misconfigured
  • GDPR/CCPA consent requirements are not being met
Resolution Steps:
  1. Navigate to Data > Unified Profiles and verify that affected users have consent attributes populated.
  2. Check the destination configuration to ensure consent field mappings are correctly defined.
  3. Review the journey’s audience segment to confirm it filters for users with valid consent.
  4. If using a custom consent framework, verify that the consent taxonomy aligns between Zeotap and the destination.

​
EVENT_PARSING_FAILED

FieldDetail
CategoryData
SeverityError
DefinitionEvent parsing or request building failed during transformation before sending to the destination.
Action TypeTechnical Fix
What it Means: The event data could not be processed into the required format before sending to the destination. Resolution Steps:
  1. Review the Map Your Fields logic for syntax errors or null values.
  2. Validate transformation logic and ensure data types align with destination requirements.
  3. Re-trigger the event after fixing the payload.

​
BAD_REQUEST

FieldDetail
CategoryData
SeverityError
DefinitionMandatory fields missing or invalid parameters in the request.
Action TypeConfiguration Fix
What it Means: The request payload sent to the destination is invalid or incomplete. Resolution Steps:
  1. Cross-reference destination API requirements with your field mapping.
  2. Ensure your Primary Identifier (e.g., external_id or email) is not null.
90% of BAD_REQUEST errors originate from a null primary ID. Validate this mapping first before investigating other causes.

​
AUTHENTICATION_ERROR

FieldDetail
CategoryAuth
SeverityCritical
DefinitionToken expired or authentication failure.
Action TypeSecurity Fix
What it Means: The destination rejected the request due to authentication issues such as expired tokens, invalid credentials, or insufficient permissions. Root Causes:
  • API token or OAuth access token has expired
  • API credentials were rotated on the destination side without updating Zeotap
  • Insufficient API permissions or scope on the destination account
  • IP whitelisting changes on the destination firewall
Resolution Steps:
  1. Navigate to Integrate > Destinations and locate the affected destination.
  2. Re-authenticate the connection by refreshing OAuth tokens or entering updated API keys.
  3. Verify the API permissions on the destination side — ensure the token has write access.
  4. Test the connection using the destination’s Test Connection feature before re-running the journey.

​
RATE_LIMIT

FieldDetail
CategoryThrottle
SeverityWarning
DefinitionDestination API rate limits exceeded.
Action TypeThrottle
What it Means: Too many requests were sent to the destination within a short period of time. Zeotap automatically retries rate-limited requests with exponential backoff. Resolution Steps:
  1. Reduce Batch Size — Configure smaller batch sizes in the destination settings to spread requests over a longer period.
  2. Add Delays — Introduce wait nodes in the journey to stagger audience delivery.
  3. Request Higher Limits — Contact the destination provider to increase your API rate limit allocation.
  4. Monitor subsequent executions to confirm resolution.

​
SERVER_ERROR

FieldDetail
CategoryDestination
SeverityError
DefinitionInternal server error on the destination side.
Action TypeExternal Check
What it Means: The destination server encountered an internal issue while processing the request. This is typically a transient error. Resolution Steps:
  1. Check the status page of the destination (e.g., Salesforce, Braze, Slack).
  2. Wait until the external service is confirmed stable before any manual intervention.
Do not manually re-inject profiles for SERVER_ERROR. The system retries automatically. Premature re-injection can result in duplicate events once the service recovers.

​
SERVICE_UNAVAILABLE

FieldDetail
CategoryDestination
SeverityWarning
DefinitionDestination service temporarily unavailable.
Action TypeMonitor & Retry
What it Means: The destination service could not process the request due to temporary downtime or overload. Resolution Steps:
  1. Wait for the destination service to recover — the system retries automatically.
  2. Monitor the destination’s status page.
  3. Replay failed events once the service is confirmed back online.
Do not manually re-inject profiles for SERVICE_UNAVAILABLE. The system retries automatically. Premature re-injection can result in duplicate events once the service recovers.

​
ENDPOINT_NOT_FOUND

FieldDetail
CategoryConfig
SeverityCritical
DefinitionDestination endpoint URL does not exist.
Action TypeConfiguration Fix
What it Means: The configured API endpoint is incorrect or no longer available. Resolution Steps:
  1. Verify the destination endpoint URL in your Journey configuration.
  2. Check if the endpoint has been changed or deprecated.
  3. Update the URL to the correct active endpoint and re-test the connection.

​
MISC_ERROR

FieldDetail
CategoryUnknown
SeverityError
DefinitionMiscellaneous error returned from the destination.
Action TypeEscalation
What it Means: The destination returned an unexpected error not categorized under standard error types. Resolution Steps:
  1. Contact the Support Engineering Team at support@zeotap.com.
  2. Provide the Request ID from the Execution Details panel.
  3. Include the Journey execution ID, error timestamp, and destination name.
If you encounter an error code not listed above, or if the issue persists after following the resolution steps, include the journey name, execution ID, and exact error message in your support request for fastest resolution.

​
Error Rate Thresholds

Use the following thresholds to determine the appropriate response for error rates in your journey executions:
SeverityError RateRecommended ActionResponse Time
Normal< 1%No action required. Log for trend analysis.N/A
Warning1% – 5%Investigate root cause. Check for transient issues.Within 24 hours
Critical5% – 20%Immediate investigation. Check destination health.Within 2 hours
Severe> 20%Pause journey. Escalate to engineering.Immediate
Last modified on March 31, 2026