Failed to find Invalid reference to fd_data._14__look_up_record.status while publishing subflow

Ravi16
Tera Contributor

I  tried to publish a subflow after performing a slight change, but I got the following Error and I am unable to publish and the status is in Draft state.

Failed to find reference to fd_data._14__for_each.item

find_real_file.png

find_real_file.png

Is there a way to find the issue and resolve it. Please help.

Regards,

4 REPLIES 4

OlaN
Giga Sage
Giga Sage

Hi,

If you have added additional actions to this subflow, I would disable action with the inline script, save the subflow, and then activate and type the script again.

Inline scripts can suffer from invalid pointers if you add or remove actions that are before the action with the script.

kshitiz11
Tera Expert

Hi Ravi, 

 

I had the same issue but no where found this solution. 

Then i did a deep dive into the whole model of Flow designer, i found the table of Output variables for Actions we create in Flow designer, and found out what's causing this issue.

 

Issue : Basically, during the creation of the Output variables under an Action, i missed to changed the "Name", and the other time i changed the name of my Action while the Internal Name of the action remains same. In order to solve this issue you need to correct the names, that's it.

 

Solution

Action : [sys_hub_action_type_definition] (check the "Internal Name" of the action should be same as in your script)

Actions : [sys_hub_action_type_snapshot] (you will variables in the Related list of your Flow Action)

Output variables : [sys_hub_action_output]  (Put the name of your Action in "Model" field and you will get the desired output variables)

Once you get to the output variables list, make sure to check the "Column name" of your variable matching the name in your script. And if the variable name is correct check for your Actions "Internal name". 

 

Mark it correct/helpful if it resolves your issue.

 

Thanks,
K Raj

NITIN46
Tera Contributor

Hi Ravi, 
This issue might be because you added a new step in between your existing flow and now the fd_data._14 is not correct step number from where you are getting the value in a script. You need to update the number 14 by new step number of flow where the variable/item is present in the script.

Thank you!  I was overlooking that I had an outdated step number in my script and updating that fixed this error for me.