Scatterplot tool - R.exe exit code indicated an error

Hello,

The scatterplot tools that are a part of my workflow are not working. They throw out a R.exe exit code error. To see if something was wrong with my data, I tried to check the official Alteryx scatterplot example. However, even this example isn’t working and giving the same error upon running the workflow. So, there seems to be nothing wrong with my data as the offiical Alteryx example also isn't working.

I found some more information on this error in the Alteryx Community, and it seems to be experienced by quite a few people. The experts are saying it’s a fake error and can be resolved by ending the R-code with a gc() function. However, I couldn't find appropriate steps to take to go ahead with it.

knowledge.alteryx.com/index/s/article/Error-The-R-exe-exit-code-n-indicated-an-error

community.alteryx.com/t5/Alteryx-Designer-Desktop-Discussions/R-tool-Fake-Errors/td-p/25163

Could someone give step-by-step instructions on how to add a gc() function to the R-code for the Scatterplot tool? I found this part extremely complicated and didn't know how to go about it.

FYI - I use Alteryx on my Mac with Parallels since the Designer cloud platform doesn't have any Data investigation tools yet.

Alteryx version: Admin 2022.1, Predictive tool package for the same version has been installed.

Error Message

Macros

Data Investigation

R Tool

Accepted answers

All comments

caltang

The link you sent: https://knowledge.alteryx.com/index/s/article/Error-The-R-exe-exit-code-n-indicated-an-error

If you scroll down, you can see that if a tool has the R Tool logo on the bottom left indicates that it has R behind the scenes. Right click on your tool and click on Open Macro like so:

caltang

If you scroll down from there, you can see the R Tool backing this Scatterplot tool.

hdesai7

@caltang, yes I opened the Macro. But, how to add the gc() function to the R-code? Where do you input that? Thanks for your help.

hdesai7

@caltangI found the R tool below. Where do I include gc()?

I tried to include it at the end. But, it's not working when I reran the workflow.

Screenshot 2023-09-23 at 2.01.50 AM.png

hdesai7

@caltang But, it's a personal machine, and I am the admin. I should have access to it, right? Do you recommend uninstalling the Admin version and installing the Non-admin Alteryx version to avoid this issue. Will I be able to save the changes to the .yxmc file if I have the non-Admin version on my personal machine??

Screenshot 2023-09-23 at 2.33.58 AM.png

caltang

I was able to save no issue, I think that's worth a try!

hdesai7

Okay, I will try and let you know.

hdesai7

@caltang I could save it now. My Alteryx folder was read only. So, it wasn't allowing me to make any changes. I added the line 'gc()' as the last line to the Scatterplot macro and saved the .yxmc file. I then ran the Scatterplot example in the main workflow.

Same error. So, the issue is not getting resolved by putting gc() in the R tool as the last line.

Any other suggestions?

hdesai7

@caltang I am also getting this new error now after adding the gc() line as the last line in the R tool.

So, there is an issue with the gc() line. It is not correct.

Screenshot 2023-09-23 at 3.18.23 AM.png

caltang

Hmm… odd. In the mean time, can you remove the gc() line and save again, then click Run & see?

Otherwise there’s this idea: https://community.alteryx.com/t5/Alteryx-Designer-Desktop-Ideas/Revisit-R-tools-fake-errors/idi-p/913454

I’ll also call in @TheOC as he is more familiar on this than I am. Will keep you posted

hdesai7

Yes, I removed the gc() line and saved it. I don't know if the plain vanilla gc() line is good enough or I need to have some additional code in there. It's the same issue even after saving again without that line.

Thanks for calling in theOC. Hopefully there is a resolution. I also emailed Alteryx support.

caltang

Hi @hdesai7 - just following up with you. Has anyone from Alteryx Support reached out to you?

hdesai7

Hi @caltang , yes, I am working with Alteryx support. Hopefully, they can come up with a solution to the problem.

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15867

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703