cancel
Showing results for 
Search instead for 
Did you mean: 

Error: Fuzzy Match: Internal Error: The incoming packet sequence was not completed be

abeljohnson
Meteoroid

Error: Fuzzy Match: Internal Error: The incoming packet sequence was not completed be

I keep getting this error. Funny thing is, it didn't happen before for the same input sources. 

 

I've also unchecked the Use of AMP Engine in Edit User Settings as recommended by other solutions. It does not fix the problem.

 

What do I do next?

 

5 REPLIES 5
abeljohnson
Meteoroid

Error: Fuzzy Match: Internal Error: The incoming packet sequence was not completed be

I keep getting this error. Funny thing is, it didn't happen before for the same input sources. 

 

I've also unchecked the Use of AMP Engine in Edit User Settings as recommended by other solutions. It does not fix the problem.

 

What do I do next?

 

Highlighted
Raj
Nebula

Re: Error: Fuzzy Match: Internal Error: The incoming packet sequence was not completed be

This error message typically occurs when there is an issue with the data being used in the Fuzzy Match tool in Alteryx. It usually indicates that there is a problem with the data's format or structure

Re: Error: Fuzzy Match: Internal Error: The incoming packet sequence was not completed be

You're right. The data types of some fields were not correct for the Fuzzy match style that was selected

Raj
Nebula

Re: Error: Fuzzy Match: Internal Error: The incoming packet sequence was not completed be

is it solved now?

abeljohnson
Meteoroid

Re: Error: Fuzzy Match: Internal Error: The incoming packet sequence was not completed be

Yes, by selecting a different field to match on

MikeD
Asteroid

Re: Error: Fuzzy Match: Internal Error: The incoming packet sequence was not completed be

I had this same issue and was able to fix it by deleting one-by-one the fuzzy matching rows from the bottom up in the Fuzzy Matching tool.  In my case, the field that was causing problems was "Suite" in address.  When I got rid of that, it ran fine.  I suspect that data field needs more cleansing, and so I will implement that next and try to add it back