"You found a bug" Error. How to resolve this?

I am using the latest version of Alteryx (Version: 2021.2.2.45235).

I used MySQL ODBC connection in my input tool, but when running the workflow it showed an error saying (Error: Input Data (772): You have found a bug. Replicate, then let us know. We shall fix it soon.)

In the previous version of Alteryx this workflow worked fine and had no issue at all.

How can i resolve this?

Thanks in Advance Found a bug error.JPG

Input

Accepted answers

All comments

CharlieS

Hi @nangia

As the message states, the resolution is to replicate the error and send all the supporting information you can to Alteryx Support so they can address the bug in a future release. Compose an email to support@alteryx.com and attached the workflow if you are able. In this case, it may just be the input tool and as much information as you can provide about the database (version, table schema, etc).

Sebastiaandb

Don't have a solution, sorry! Older posts refer to the support page and submitting a ticket :-).

https://community.alteryx.com/t5/Alteryx-Designer-Discussions/You-have-found-a-bug-Replicate-then-let-us-know-We-shall-fix-it/td-p/438590

Have you tried to make the connection again via ODBC, Quick connect and as a in-db connection? I can imagine that you want to use the input tool (and not in-db).

nangia

Hi Sebastiaan,

Yes, I have tried that as well. Deleted the old input tool, and replaced with new input tool and made the connection again, still the error remains.

CharlieS

Good idea,m @Sebastiaandb: Let's talk about that connection.

The Alteryx support page on MySQL offers a few additional driver options to configure your connection to the database that might be work investigating. This also lists the database and driver versions that it was tested on:
https://help.alteryx.com/20213/designer/mysql

Database Version: 8.0.25
ODBC Client Version: 1.1.2.1002

Another course of troubleshooting would be to modify the query to see if there's something about the syntax/operations that is causing the error. Try modifying your query to see if there's a specific part that is casuing the error. Share any information you can and I'm sure the Community will continue to chime in and help.