How to resolve "Unhandled error: integration terminated early" errors

In testing new sources or in regular use, occasionally, you may run into the error “Unhandled error: integration terminated early.” This article shows through examples how to get more information about and correct the cause of the error.

Background: Leads coming into a LeadConduit flow are processed through source integrations. Most sources are set up to use the LeadConduit Standard integration, but there are specialized integrations that will automatically be added to LeadConduit when you select a standard source on the sources tab. Source integrations, listed next to sources in the Sources tab, have limitations and adaptations to particular use cases, and enforce syntax according to the HTTP Content-type and the Methods allowed.

Finding the cause: look carefully at the lead that has encountered the error

1. Click on a lead from the Leads ->Lead Events viewer.
2. Click on the Error step on the left, which displays “Unhandled error: integration terminated early.” This error, issued by the source integration being applied for this source, directly follows the incoming submission to the flow.
3. Expand the Technical Details at right.

Example 1: Problems in lead data

The error displayed below in the Technical Details for this example is:

Unable to parse JSON – SytaxError: Unexpected token
in JSON at position 693

The next step in correcting the error is to examine the incoming json to find the offending character in the position mentioned:

1. Click on the incoming source step at top left
2. Expand the Technical Details on the right and examine the packet sent in for errors

The error, in this case was a newline inserted in a value, circled here in red. To fix this error, the account worked with the lead supplier to adjust formatting in their lead submissions.

Example 2: HTTP Method incorrect

The error displayed below in the Technical Details is:

The GET method is not allowed

The error signals the submission was using the wrong HTTP Method. This could be explained by one or two of these:

• the submission was using a GET, but the source integration being used does not allow GET
• the “submission” may have been just a random click on the submission URL, launching a browser and sending a blank lead (which is common when a vendor is working initially to implement the leads)

To fix this error, the vendor used the POST method for subsequent leads.

• Screenshot_2023-05-24_at_6.18.40_AM.png80 KB
• Screenshot_2023-05-24_at_6.19.12_AM.png200 KB
• Screenshot_2023-05-17_at_9.03.39_AM.png70 KB