Performing assignment in spinoff flow causes error

Using v7.3.1

I have a very simple spinoff flow that creates one assignment. Once that assignment is performed, the spinoff flow should end.

When I perform the assignment and click 'submit', I get the error "The reference .pxFlow() is not valid. Reason: contains empty subscript(s)”. The logfile confirms this is an InvalidReferenceException.

The tracer shows the exception happening in step 24 of activity Assign-.CompleteAssignment, which is a Java step that uses the final function StartFlow, which has the further potential to call other final functions. This step and the functions use the local parameter refFlowName to form the correct reference to .pxFlow(). I have confirmed refFlowName has the correct value at the time StartFlow is called, such that the reference should be .pxFlow(QualityCheck). However, since all the functions called are final, I cannot determine where or why the invalid reference is being formed.

Any ideas how I can get rid of this error so my spinoff assignment completes properly?

***Edited by Moderator: Lochan to update platform capability tags***


Keep up to date on this post and subscribe to comments

August 23, 2019 - 3:02am


It will be difficult to tell you without a tracer output. Can you share a tracer XML?

August 23, 2019 - 12:32pm

Thank you for your reply, Marc. Attached is a zipped version of the tracer XML file.

August 23, 2019 - 1:02pm
Response to GlenCaldwell

Yes, this is strange, how about if you try to resume another one then still the same issue. I think you should try to simplify the scenario to better understand where the problem is coming from

August 23, 2019 - 1:41pm


I appreciate the suggestion, but it would be difficult to simplify the process further. In fact, this flow was intended as a demo to my client about how I could spin off an assignment. It is purely proof-of-concept, and doesn't actually do anything. The main flow has 2 very simple assignments, and this spin-off has one. There is no pre or post processing of any kind. When I call the flow as a normal flow (not a spin-off) it works fine. However, I need the spin-off functionality when I begin to build out the real process.

An exception I can see in the Tracer XML seems to indicate the RemoveFlow function might be throwing the exception. However, as all functions called from step #24 of CompleteAssignment are final, I cannot determine where or why the flow name is not getting passed.

August 26, 2019 - 5:23am
Response to GlenCaldwell

Could you still have flows on draft mode maybe.

August 26, 2019 - 12:49pm

I did have the main flow and spin-off in draft mode, but this is a development system where I am showing the concept, and then need to begin development to implement it. I have taken both flows out of draft mode with the same results, however. I think I'll need to raise an SR for this issue.


August 27, 2019 - 10:43am
Response to GlenCaldwell

Could be needed yes let us know the SR number anyway

August 27, 2019 - 3:52pm

I have decided to start my QC flow from a local flow action instead of using a spin-off.