The Zurich release has arrived! Interested in new features and functionalities? Click here for more

Sub-Flow Output Error in Flow?

Matthew Gill
Tera Expert

I am calling Sub-Flows within a Flow. The Sub-Flows return [status] which is a True/False variable. The Sub-Flow tests correctly, but when it is called from the Flow the Sub-Flow completes, returns the appropriate output when looking at the subflow execution details, but the Flow execution details show an error for the Sub-Flow task. 

It is as if the Sub-Flow output variable is not being passed back to the Flow. I have ensured that the variable types are the same, and the Sub-Flow is set to 'Wait for Completion). Any advice or guidance is appreciated. Thank you!

1 ACCEPTED SOLUTION

Matthew Gill
Tera Expert

Alright... Support figured out what the issue was.

 

Even though the error was being shown on the Sub-Flow call, the issue was actually failing on the Update Record Action. Specifically, updating the 'Actual Start' field. I was updating to " return ( new Date() ); "; however, that field requires a String, for some reason, and was not giving a good Error Code. The workaround is to update to " return ( new Date().toString() ); ". Not ideal, but it works...

 

Thanks everyone for helping!

View solution in original post

20 REPLIES 20

Okay, that's an issue for sure.

Do you get the same result if you checked/unchecked the "wait for subflow to complete"?

Might be a bug, so I would contact support to get additional help.

I appreciate the guidance and advice. I have a ticket with support. I will reply once I get some info back. Thanks everyone!

This is a little concerning. I hope support raised this to the developers, because if you manage to create a stack overflow with this, it implies that the XML parser is not very robust.

Just my 2 cents.


If this post was helpful, I would appreciate if you marked it as such - thanks!

Best
Daniel

Matthew Gill
Tera Expert

Alright... Support figured out what the issue was.

 

Even though the error was being shown on the Sub-Flow call, the issue was actually failing on the Update Record Action. Specifically, updating the 'Actual Start' field. I was updating to " return ( new Date() ); "; however, that field requires a String, for some reason, and was not giving a good Error Code. The workaround is to update to " return ( new Date().toString() ); ". Not ideal, but it works...

 

Thanks everyone for helping!

Good that it's solved, please also close this thread by marking your own answer as correct.