Flow LookUp Records Filter Carry Over Condition Suddenly

[Charles Platt]

I've been working on a flow that triggers on a field changing from a particular table. I finally got to work after manipulating the trigger and look up records. All of a sudden the flow stopped working properly due to the filter conditions no longer populating the information within the look up records action. I've added screen shots. Nothing was changed in these actions to cause this and I'm not sure of where or what to look at for this type of situation.

I even compared to when the flow was running properly and this filter condition that's no longer present which throws the entire flow off.

Has anyone ever encountered this before? Any assistance would be greatly appreciated.

[AnirudhKumar]

Hey Charles,

I have a feeling it might be related to access. Could you log the value just before this action executes, and see if for the person executing the flow if the log returns a value?

If it doesn't, then try executing the flow as admin (Set the property Run as admin = true)