Bug - Case Sensitive arguments

I just spent a couple hours searching for a bug in my flow, and I now realized that it was due to one out argument being upper case when being lower case in the outer flow. The value of the out-argument did not get out, but on runtime I did not get the usual error of mismatching arguments.

Flow A calls Flow B to get a boolean value. Flow B as an out argument “ReturnValue”. When Flow A calls Flow B its outargument is named “returnValue” (note the lower case R). The error is that the value of Argument is not passed out to Flow A, but an argument mismatch error has not been raised to notify me of this.

1 Like

I faced a similar issue. UiPath wouldn’t notify me of the issue and was giving me a random error(Get credential : Asset name cannot be empty). A restart solved it and UiPath then gave a different error message which pointed me in the right direction.

There are certain inconsistencies with the way arguments are used. Arguments, when being passed in or out, are case sensitive. But inside the flow, the arguments behave like variables(Case insensitive). This added to the confusion and delayed the solution for me.