Workflow using Test Values

[jeevenugo]

Hi everyone,

I'm trying to run my ReTool workflow, but it keeps using the Test Parameter values. I'm running the Workflow from my application using the below value and it shows up as 'TEST' in the workflow history.

The actual UUID value:

The Workflow using "Test" as the actual value

[bobthebear]

try going into the settings for the UGO DB resource, I haven't used this one before, but I think you should see

or something similar. trying enabling 'Disable converting queries to prepared statements'. not sure if this will fix it for you, but worth a try

[jeevenugo]

Sorry I should've mentioned i'm not hosting my data on ReTool, i'm using a postgresql database.

[bobthebear]

the setting should be at the bottom there also:

[jeevenugo]

I appreciate your help on this matter, but I'd rather not disable that feature. SQL Injection becomes a concern at that point and I'd just rather not deal with that.

[jeevenugo]

@joeBumbaca @Tess Would you guys be able to help out here?

[Tess]

Hi @jeevenugo I can try to do some testing! Are you triggering the Workflow from the app with a rest query or the Workflows integration?

[Tess]

I haven't been able to reproduce this issue yet.

Any chance you could share an export of the Workflow?

Did you double check the latest version of the Workflow was deployed?

Thanks!

[jeevenugo]

Hi @Tess Thanks for taking a look, the issue doesn't seem to appear anymore, nonetheless, I've attached the workflow json.
UGO Insert Company.json (16.0 KB)

[Tess]

Hi @jeevenugo,

Thanks! I'm glad it's working for you now. I see in your screenshot that you're not triggering the workflow from another workflow* but I wanted to give you a heads up that it looks like we have a bug where the test values are used if the workflow is triggered by another workflow and that other workflow is using JSON workflow params (using Raw params instead of JSON should be a workaround):

Maybe what you were running into is related Keep me posted if you notice it again

[liamrohan]

Hi @Tess .

We've a workflow that for some reason 'Test JSON Parameters' is overriding the raw JSON passed in via a webhook trigger. What's more the workflow was working as expected in production; using the JSON payload inside startTrigger.data as expected. However, all of a sudden the workflow now ONLY uses the test parameters, even when the required payload is passed in (nothing has changed).

Unfortunately I can't export the workflow here as it contains sensitive credentials. If you'd like to take a look I can possibly duplicate it and remove the sensitive parts, please let me know.

Thanks,
Liam

[Tess]

Hi @liamrohan thanks for chiming in! Sorry to hear this is happening

I haven't been able to locate your account - could you confirm which plan you're on (Cloud or self hosted)? If self hosted, which Retool version #?

Yes, if you can share any version of the workflow it could help us try to reproduce the issue. Keep mind that resources don't work in exports, so I won't be able to query any resource data. Also, could you share one of the Workflow Run Ids from the logs?

[jeevenugo]

Hi @Tess

Starting to see this bug again. We're calling this workflow from our app using the JSON format.

See attached picture and json

UGO Update Company.json (20.1 KB)

[jeevenugo]

@Darren Any thoughts on this, quite debilitating for my application that I can't run workflows properly.

[bobthebear]

have you tried removing the test json and leaving the area blank? I'm curious if it will be forced to use the sent data since there is no test data or if it will try and use null

[Tess]

Sorry to hear!

Previously, I found a bug where ternaries (see hello in the JSON below) in the app were causing the workflow to use test inputs:

Though I haven't been able to reproduce it with your workflow yet

Are you using ternaries in your JSON? If not, could you share a screenshot from the app too (or an export)?

Since you mentioned it is debilitating (understandably), I might try calling the workflow from a REST query just to check if that could be a temporary workaround

[jeevenugo]

Thanks for getting back to me @Tess , however, no ternary operators, just normal input.

[jeevenugo]

Hi @Tess ,

I'm not sure if this is the fix, but this issue occurred again, however, this time one of my inputs was red, it had some issue with the select component being null, I was using '.selectedItem.id', when I changed to '.value' and ran the workflow, it ran successfully.

[Tess]

Hi @jeevenugo That behavior is reproducible! Thank you.

Please keep us posted if you notice any other issues