Slowness on Activate button on Flow Designer caused by unreferenced fieldsDescriptionCustomer was facing slowness issue on a Flow when clicking on "Activate" button.CauseFrom the logs we were able to find that there is a unknown field 'quiescence' in table which is not referenced properly and it is stopping Flow Designer to be activated. Logs: =======================================================================================================================================2020-03-03 15:39:31 (693) Default-thread-13 9727F7CA1BD744502A4E8597DC4BCB6C txid=8ff8f7821bd7 WARNING *** WARNING *** getGlideElement called for unknown field 'quiescence' in table 'sys_hub_flow_logic'2020-03-03 15:39:31 (693) Default-thread-13 9727F7CA1BD744502A4E8597DC4BCB6C txid=8ff8f7821bd7 WARNING *** WARNING *** setValue called for unknown field 'quiescence' in table 'sys_hub_flow_logic'2020-03-03 15:39:31 (752) Default-thread-13 9727F7CA1BD744502A4E8597DC4BCB6C txid=8ff8f7821bd7 WARNING *** WARNING *** getGlideElement called for unknown field 'quiescence' in table 'sys_hub_flow_logic'2020-03-03 15:39:31 (752) Default-thread-13 9727F7CA1BD744502A4E8597DC4BCB6C txid=8ff8f7821bd7 WARNING *** WARNING *** setValue called for unknown field 'quiescence' in table 'sys_hub_flow_logic'======================================================================================================================================= Please check below screenshot to see when there is an unreferenced/Unknown field, it will be shown as [record] instead of actual field name. Check actions highlighted in the below screenshot. ResolutionCreating flow from scratch will help resolve configuration issues. Make sure before you remove any fields from flow, which are not referenced in the later part of flow. Please consider testing in subprod instances before moving to prod instances.