Failed to find reference to fd_data._30__look_up_record.status while publishing subflow

[Naresh Kumar G1]

Hi All,

I am new to Service now workflow development. I tried to publish a subflow after performing a slight change, but I got the following Warning and I am unable to publish and the status is in Draft state.

Failed to find reference to fd_data._30__look_up_record.status

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

Regards,

Naresh

[Maik Skoddow · Accepted solution]

Hi @Naresh Kumar Gnanakrishnan ,

you said, you performed "a slight change" and this probably the reason for the error. 

Each time you drag a data pill into your flow an internal reference is created. So in case you remove or change anything on a action at the beginning of your (sub-)flow then following actions cannot refer any more on the preceding actions.

Without any further details you are the only one who can find out which changes have been done and which implications they have.

Kind regards
Maik

If my answer replied your question please mark appropriate response as correct so that the question will appear as resolved for other users who may have a similar question in the future.

[Maik Skoddow]

Hi @Naresh Kumar Gnanakrishnan ,

Did my reply answer your question?

If so, please mark appropriate response as correct so that the question will appear as resolved for other users who may have a similar question in the future.

If not, please tell me what you are still missing!

Kind regards
Maik

[Eivind Sandnes]

Hi!
I have the same issue with one of my flows at a customer. The error mentions a reference that is no longer there, so it's kind of hard to know what was moved.

"Failed to find reference to fd_data._32__get_flow_outputs.step_output_code"

Is there any way to remove old references in a flow? I really don't want to create this flow again from scratch... 🙂

UPDATE!

Found out I had referenced it within a code-snippet in the same flow 😂

[rupalipati]

I encountered a similar issue where an error message, fd_data._12__look_up_records.count, appeared when trying to save the subflow. After updating the flow, I validated all the steps following the 12th step and discovered the problem was with a scripted field referencing the 12th lookup record. However, after my changes, the lookup record had been moved to the 14th step.