Performance issue in ESC portal due to sn_ex_sp_pro_web_application where app source ='Azure'Issue ProblemUsers reported significant delays in processing Service Catalog requests within the Colleague Centre, including form processing, comments, updates, and system responses. The issue was observed during regression testing on a Test instance upgraded to Australia Patch 4 HotFix 1. Initial investigation identified sustained system load (semaphore usage fluctuating between 10 and 12) and a long-running 'Article Optimization - Scripted' transaction, which was manually terminated but did not resolve the issue. Further analysis revealed a slow transaction related to an SP widget (/api/now/sp/rectangle/698658015c7b7010f8777b70dd6b8d03) causing session waits and impacting performance. Facts There are two ways to create these records: using the "Update applications" UI Action on the table, or activating the "Fetch application" scheduled job. Both ultimately run the "Fetch applications" subflow. That subflow then looks for the Azure tenant's app registration and creates or updates the corresponding records in the sn_ex_sp_pro_web_application table. The scheduled job is shipped inactive OOTB, so these Azure-related records will not be created unless someone activates it. Release All Cause Root Cause1. A large number of Azure application records in the 'sn_ex_sp_pro_web_application' table caused performance degradation during widget rendering, as the system checked access for each record sequentially.2. The 'Fetch application' scheduled job, if active, contributed to maintaining these records, leading to sustained system load. Resolution 1. Review the 'sn_ex_sp_pro_web_application' table for Azure-related records and deactivate them if they are not required, as they contribute to performance degradation during widget rendering.2. Verify the status of the 'Fetch application' scheduled job (sys_id: 48b46a8a4744c1109dcae052846d43cf) and ensure it is inactive unless intentionally enabled, as it creates or updates Azure application records.3. Monitor the instance for recurring performance issues and collaborate with the Service Portal team to address underlying configuration or flow-related concerns.