The "Get Catalog Variables" Flow Action will return Outdated VariablesDescriptionUsing the "Get Catalog Variables" Flow Action multiple times will return Outdated Variables.Steps to Reproduce Import the attached update set.This creates "Test Item" with the flow "Test Flow Designer" as the process engine.Make sure that the flow reporting is on.Go to Process Automation > Properties and change the value for the flow reporting to Developer Trace.Submit the item "Test Item."Go to the created Requested Item and inspect the flow contextExpected: The Value is updated in the "Log" action, and the Get Catalog Variables should return the updated value.Actual: The value returned by the Get Catalog Variables action is outdated. The returned variable still holds the old valueWorkaroundThis is expected behavior and by design in all currently supported releases. Reasoning: The "Get Catalog Variables" Action is in sync with the "Look Up Record" Action and it will retrieve the values from that GlideRecord. Therefore if you retrieved the GlideRecord at the start of the Flow but use it later in the "Get Catalog Variables" Action then you are providing an outdated GlideRecord and it is expected to return these values. Issue Prevention: You can use a "Look Up Record" Action on the Step before the "Get Catalog Variables" Action to ensure that you are collecting the Values from the Database and they will be up to date. As an alternative option you can also use the following: Please set the "Submitted Request Item" Input to the "Get Catalog Variables" Action to use a newly generated GlideRecord for this Request ItemYou can do this by using the following Script instead of the Request Item Data Pill Script Input: var gr = new GlideRecord('sc_req_item');gr.get(fd_data.trigger.request_item.sys_id + '');return gr; Example:Related Problem: PRB1552422