Failed Events in a Pipeline

Whenever Hevo finds that an Event cannot proceed ahead in the Pipeline, it marks the Event as Failed. Some key causes of Event failures include:

  • Schema incompatibility and conflicts. The schema of incoming objects does not match the schema of the Destination object. This may happen if the Source schema has changed over time or if you have mapped fields of incompatible types between Source and Destination.

  • Transformation related errors. Transformation code provided by you may have bugs.

  • Incorrect mappings. There can be errors while manually mapping Source and Destination tables.

  • Transient Errors: Some Events may be marked as Failed to avoid ingestion overloads, and are errors that Hevo is able to recover from on its own, without needing any action from your end.

  • Network failure. On a rare occasion, Hevo may encounter network or connectivity failure with your Destination.

See section Reasons for Event Failures for more details.

Failed Events are held by Hevo for 30 days, after which they are purged permanently. Purged Events are not replicated to your Destination. Hence, Hevo recommends that you resolve all failed Events within 30 days.

If the Events are sidelined due to un-mapped Event Type, they are retained only for seven days and are deleted post that.

Viewing Failed Events

All the failures requiring action from you are made visible on the Pipeline Activity section in the Pipeline Overview tab for inspection.

Click on the Events Failed count to get a detailed list of failed Event Types and their failure reasons. You can also view the Number of Events for each failure reason.

Note: The Events Failed count and the failed Event Types list do not include Event Types that you have skipped during schema mapping.

Details about failed Events like failure reason, Event Type, and number of Events

Click on VIEW SAMPLE next to a failure reason to browse through few of the failed Events from that category. Click the Copy icon to copy a failed Event’s JSON representation or the Download icon to download the entire sample of failed Events.

You can also view sample failed Events for an Event Type from the Pipelines -> Transformations page.

To do this:

  1. Click the Select Event Type drop-down.
  2. Enable the Events not Loaded option to view only the Event Types with failed Events.
  3. Select the required Event Type and click GET SAMPLE.

    View sample failed Events




Revision History

Refer to the following table for the list of key updates made to the page:

Date Release Description of Change
23-Mar-2021 1.59 Added steps to the section Viewing Failed Events for viewing sample failed Events through the Pipelines -> Transformations page.
Last updated on 25 Mar 2021