I'm calling a workflow from an app, and at some point the workflow started always being called with the Test JSON parameters instead of being called with the workflow parameters I've defined in the app
The app configured ^^ is not capable of sending a limit of 50 (it always sends -1 or 100) and is not capable of sending the elm string "no", but that is how the workflow is being triggered.
Is there any way to debug why the workflow's inputs are being ignored?
How are you calling the workflow? I can't tell from that screenshot where it's happening or via what method.
Also, double check the latest version of your workflow is actually deployed, not just saved. There is a difference when it's being called externally.
I did some more experimentation and discovered the following:
If I have this JS code, which Retool shows as evaluating to zero, as my argument to include_not_in_a_course, then the workflow gets called with the test JSON parameters
However, if I change this to just be the constant zero, then the workflow gets called correctly with the intended, non-test, parameters
Huh! And if I then take that ternary expression and put it in a separate transformer, so that the JS expression is simpler, the query works again (it is called with the expected parameters not the test parameters)
This makes me thing there's some way that Retool is getting confused because the JS expression is somehow "too complicated"
Also @MikeCB, to answer your question: I'm calling the workflow inside a Retool app on the onClick event of a button.
Thanks for reporting this! I am able to reproduce it on our side. I have reported this to my team internally & will follow up here when I have a fix
