Flow Designer getGlideElement / setValue called for unknown field 'quiescence' in table 'sys_hub_flow_logic'Issue Seeing the following error / log message in the instance logs: *** WARNING *** setValue called for unknown field 'quiescence' in table 'sys_hub_flow_logic'*** WARNING *** getGlideElement called for unknown field 'quiescence' in table 'sys_hub_flow_logic' There are several symptoms associated with this Error Message. These symptoms include (but may not be limited to): Slowness when loading Request Item List ViewSlowness when loading Request Item / Catalog Item Form ViewSlowness when activating a FlowFlow is freezingCauseThe 'quiescence' Field has been added to the Flow Designer as part of the Paris Release. If you are seeing this error on an instance below Paris Upgrade (E.g. Orlando) then it is likely that the Users have exported and imported a Flow / Subflow / Flow Action from a Paris instance. Since this field does not exist in the earlier releases. It can then cause this error to loop and display in the logs. Ultimately, this can cause a wide range of issues on the customer instance.ResolutionPlease advise the Customer that importing Flows from a higher version is not supported and is known to cause many issues within Flow Designer and also other Products which it interacts with (e.g. Service Catalog). Steps To Resolution: Identify the Flows which have been imported from Paris (Ask the Customer for this information)Remove the Flow / Flow Action which is from the wrong versionRe-create the item in questionDeactivate and re-activate the Flow to ensure it is re-compiledRelated LinksIf necessary, an entire Flow will need to be re-created in the instance. While this is not always an optimal solution - it is required as a result of the imported records containing different data structures to older versions of Flows. This is the best way to ensure that the Flows being used are formatted and compiled for the version on which they are running. Otherwise we are likely to see issues such as the above. For this reason it is important we ensure the Customer understands that imported Flows should only come from instances on the exact same version as the target instance.