Runner macro errors - workflow runs without error

[NeilJB]

I have a runner macro followed by a number of conditional runners (screenshot attached). The Runner gives an error

"ConvError: Runner (2): Tool #31: Errors: ( is not a number."

preventing any of the conditional runners to run.

The Runner runs a basic Alteryx module (screenshot attached) with a SQL query pulling in StoreID from a database and saves this to a .yxdb. The module runs without any warnings or errors when I run it in Designer.

I have used the select tool to switch off every field except StoreID - I get the same error from the Runner tool.

I have edited the SQL query to only pull in the StoreID field - I get the same error.

I have tried all types of string type and length for the StoreID in the select tool (StoreID is always 27 chars). Same error.

NB The SQL query runs without error in SSMS. The output contains no "(" characters (using PFE to search text).

I saw the same topic discussed here where the user changed format of an input CSV file. This solved their problem. Can I change the format of data queried via SQL?

Any other approaches please? I've run out of ideas! Thanks!

[Peachyco · Accepted solution]

Might be some weird, hidden characters in your StoreID field. Are you sure that this field is clean (e.g. if it's entered manually, there's a big chance that it's not clean)? Maybe try positioning the Data Cleansing Tool (and similar tools) first to remove weird characters and extra whitespace before the data get passed to the Select Tool.

Also, yes, you can cast the column to a different data type in the SQL itself. The code might vary with the specific database system that you're using so you will have to look that up to get it right.

On another note:

If you want the rest of the Runners to run even if one of them throws an error, you can Union the success ("S") and failure ("F") output of each Runner before connecting to the next Runner. This makes sure that a signal is passed to the next Runner so they get to run regardless of the failure/success of the previous Runner.

[NeilJB]

I tried putting the data cleansing tool first with no effect. But I need to keep non alphanumeric codes in (to maintain unique IDs), so can only remove whitespace.

But the union S + F idea works!  Results look correct at first glance (but I will compare outputs from Runner vs individual workflows approaches).

Interestingly, a colleague has Alteryx version 2021 (mine is 2023) - he doesn't get the error, while I do.

I'm hearing this is perhaps a Unicode issue. With my very limited knowledge, I think that SQL is outputting Unicode and Alteryx is treating it as Ascii?

Thanks for all your ideas, Peachyco! Got me to where I need to be, really appreciated.