Issues with JSON params fails to send json to another workflow

Workflows
,
1

When calling a workflow from another workflow, the JSON will not pass to the workflow parameters if there are any errors in the JSON fields.

The problem is the linting does not show any issues and there is no error stating the parameters can't be sent. Instead it uses whatever was set as the test example JSON of the sub-workflow.

For example, I was trying to use .join() on an empty string because I didn't properly check for a null param. This caused a JS error that is not caught or linted. But it took me forever to figure out that was the problem. I just thought Retool had a bug.

CleanShot 2024-08-27 at 14.23.28@2x
CleanShot 2024-08-27 at 14.23.28@2x1372×280 40.3 KB

CleanShot 2024-08-27 at 14.24.18@2x
CleanShot 2024-08-27 at 14.24.18@2x1036×1824 231 KB

2 Likes
2

Hey @Adam_Patarino - welcome to the community. :slightly_smiling_face: And thanks for reaching out! This is great feedback. I've reproduced the issue on my end and will talk to our team here about potential fixes. I'll share any updates here as soon as possible.

Out of curiosity, how would you want this to fail? My initial thought is to have the parent workflow fail loudly and not run the child, at all. Let me know what you think!

3

Yeah that feels like a great option. Ideally, when you hit test, the step fails loudly and tells you there's a parsing error or something. Similar to how the response step fails when there are formatting issues in the response JSON. It would be very helpful to show where the parse error happened or log any additional details to help debug.

1 Like