Flow Execution Details When Flow Reporting (com.snc.process_flow.reporting) is turned OFF/ONFlow Execution Details When Reporting is Turned OFF/ON Table of Contents 1.Overview2. Enable Flow Reporting3.Heavy Flow Usage Memory Issues4.Questions 1.Overview In Rome Upgrade, Flow Reporting com.snc.process_flow.reporting is turned OFF by default.Therefore, any flows that was executed during this setting will cause the execution details unable to view. If the property is ON, only the new flow executions will show the details. Disabling reporting enables flows to run faster, reduces their memory footprint, and reduces disk space required. Enabling reporting in subprod development environments is recommended: com.snc.process_flow.reporting.level = ONIf reporting is required in production, please do so on a per flow basisFlow Designer > SettingsReporting is always enabled when using the Test button for that particular execution only 2. Enable Flow Reporting In Rome when you click on Flow Executions you get an error: Flow reports are not available. Check system property com.snc.process_flow.reporting.level. Flow reporting is turned off by default, and this is the reason flow contexts are not available. To activate reporting globally, configure the com.snc.process_flow.reporting.level system property. Once you turn on that system property, only the new flow executions will show the details. Activate flow reporting Our suggestion is to keep the global reporting property off in production. If it needs to be activated for troubleshooting, do it on a per flow basis not for all flows. Then once the investigation is complete turn it off again. In subprod, it can probably remain on globally although it can still cause memory performance issues. 3.Heavy Flow Usage Memory Issues KB0995284 In instances with heavy flow usage, reporting data is contributing to the massive growth of the sys_json_chunk table. 4.Questions 1) What is the intention behind turning off the com.snc.process_flow.reporting in Rome by default ? Flow reporting requires us to keep a lot of data about flow executions in memory and then in the database after flows goes to waiting or completes. Our intention is to reduce performance issues related to flow reporting. When memory issues happen they are very serious and will likely lead to P1 customer cases. 2) Is ServiceNow recommending to turn off the property after upgrade gets completed as well? Yes, we continue to recommend customers keep reporting off in production. If it needs to be activated for troubleshooting, do it on a per flow basis not for all flows.3) Can ServiceNow turn the property back to ON after upgrade (or) is it the manual step which customer need to take care after upgrade gets completed? It is a manual step to turn reporting back on follow Activate flow reporting 4) If flow reporting was off and now it's on - can we retrieve the extracted reporting data from while flow reporting was turned off? No, it's not possible to retroactively retrieve reporting data that was not retained. 5) If customers go with turning on the property globally , What kind of performance issues customer can experience? Flow reporting requires us to keep a lot of data about flow executions in memory. When memory issues happen they are very serious and will likely lead to P1 customer cases. i)Is it going to impact whole instance with all the transactions?ii)Is it going to impact flows executions where it will take more time to open ? (or) is it going to impact the flow designer. It could be fairly isolated to flow designer or it could impact the entire instance. It can vary depending on how many concurrent "large" flow executions are happening. If there's a single execution, then it could likely impact only that flow's performance, but it could impact a whole node or all nodes on the instance if there are many similar flow executions. 6) Can we auto-increase memory if flow reporting is consuming too much memory? Auto increasing memory isn't something our system architecture supports. 7) What are we doing to fix this? We are continuing to optimize our flow engine to reduce the amount of memory required and reduce your risk of encountering memory issues. Even with our best efforts to reduce the memory impact of reporting, we still recommend you keep reporting turned off in production. 8) Is there any table where can view memory usage of each and every node allocated vs Used to our production instance? If Yes , Can you please share? I know there is something in System diagnostics page to understand Memory usage , We are looking for the table which captures that information , So that we can set some internal monitoring when this happens along with the ServiceNow Monitoring the nodes? We (Service Now) proactively monitor the hosted instance for all customers. Our internal system will alert us when various thresholds are reached. Please review the following KB. KB0529232 ServiceNow Monitoring - Overview and Insight If any node experiences memory and performance issues, an internal P2 Alert and case is created. Our performance TSE will get in touch with you in 2 Hrs. We do this for all customers. Please refer stats.do page for more information.