# Salesforce: Feature Perf Degradation: Core Service - Impact (vendor’s label): minor - Status: resolved - Started: 2026-07-24 20:01 UTC · Resolved: 2026-08-01 03:30 UTC · Duration: 7 d - Updates: 12 · Affected components: Core Service, 977 instances - [Vendor status page: https://status.salesforce.com/incidents/20004309](https://status.salesforce.com/incidents/20004309) - [Company: Salesforce](https://rewindex.com/company/salesforce.md) ## Timeline of updates - **update** 2026-07-29 08:51 UTC: We’re aware that multiple customers with the Transaction Security Policy enabled are experiencing issues with report exports. Each export attempt triggers a repeated authentication loop, preventing the export from completing. The issue is impacting both production and sandbox environments. We've identified the trigger as a recent change and are working on a fix. We'll provide an update in 30 minutes or sooner if additional information becomes available. - **update** 2026-07-29 09:50 UTC: We’ve identified a recent change as the trigger and are working to develop a fix-forward. An approval is in place for this fix forward. Once approved, the fix will be then tested for its effectiveness and deployed to the impacted instances to restore services. We'll provide an update in 30 minutes or sooner if additional information becomes available. - **update** 2026-07-29 10:26 UTC: We're currently testing the fix in a test environment to confirm the fix works as expected. Once testing is complete, the fix will be deployed to the impacted instances and is estimated to take several hours. We'll provide the next update upon a significant change or when more information becomes available. - **update** 2026-07-29 10:41 UTC: A Known Issue article, which includes an available workaround, can be found here: https://help.salesforce.com/s/issue?id=a02g7000006Yoa1AAC. Customers can apply the workaround to continue operations while the fix is being deployed. Note: If you've applied any workaround steps, please ensure they are reverted once the fix has been deployed. We'll provide the next update upon a significant change or when more information becomes available. - **update** 2026-07-29 14:18 UTC: Customers with the Transaction Security Policy enabled are experiencing a repeated authentication loop when exporting reports over 10,000 records, preventing exports from completing. This impacts production and sandbox environments, including Hyperforce and GovCloud, and is linked to a recent release. The fix is ready to be deployed to two test instances and is expected to take two hours to complete validations. Following successful validations, the fix will be deployed across all impacted instances. As a temporary workaround, customers can disable the Report Export Transaction Security Policy. If applied, please re-enable the policy once the fix is deployed. We’ll provide another update as additional information becomes available. - **update** 2026-07-29 18:28 UTC: The staggered deployment continues to progress without issue. The fix resolves the authentication loops affecting report exports for customers with Transaction Security Policies enabled. As we deploy the fix to each instance, we will post an instance-level update confirming the resolution time. Once we confirm that your instance is resolved, please re-enable the Report Export Transaction Security Policy if you previously disabled it as part of the temporary workaround. We'll continue to provide updates as more information becomes available. - **update** 2026-07-30 18:41 UTC: Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward. - **update** 2026-07-30 20:06 UTC: While we previously indicated this issue would be resolved after deploying a fix, upon further investigation, we have identified additional underlying issues intermittently affecting report exports. We are actively investigating this further to resolve the issue as quickly as possible. We apologize for any confusion this may have caused and will continue to provide updates as more information becomes available. - **update** 2026-07-31 04:32 UTC: We have the initial fix deployed to a limited number of instances which did not fully resolve the issue. We identified two issues affecting report exports. Longer-running exports can fail due to repeated authentication prompts, and some exports may also intermittently need a retry to complete successfully. We're actively working on two mitigation efforts in parallel: A temporary configuration change to reduce immediate customer impact by letting longer exports complete, and a permanent fix for the underlying authentication flow, which we're developing and validating now. We'll continue to provide updates as more information becomes available. - **update** 2026-07-31 09:37 UTC: We continue to make progress on the report export issue. The temporary fix, which extends the authentication wait period to improve report export reliability, has been validated and will be deployed to a test environment before production rollout. The rollout will take some time to complete. In parallel, we continue to make progress on the permanent fix for the underlying authentication flow. We will continue to provide updates as more information becomes available. - **update** 2026-07-31 18:36 UTC: Validation and testing of the authentication wait period was successful in our test environments. We will begin rolling this fix out during regional off-peak hours through a staggered approach across all impacted instances and will follow the progress closely. This is expected to take several hours to fully complete, and we will provide updates to this post as the release develops. We will continue to provide updates as more information becomes available. - **update** 2026-08-01 05:14 UTC: At 20:01 UTC on July 24, 2026, a feature degradation began impacting Lightning report exports. Customers with the Report Export Transaction Security Policy enabled encountered a repeated authentication loop when exporting reports over 10,000 records, preventing exports from completing. Some customers also experienced intermittent download failures requiring a retry. We deployed an initial fix that resolved the internal server errors customers were seeing. As we continued to investigate, we found the remaining authentication loop was caused by an authentication window that was too short for larger report exports to complete before it expired. We extended this window and validated the change before rolling it out. At 03:30 UTC on August 1, 2026, we completed deployment of this fix to all affected instances. Report exports are now working as expected for all affected customers. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. --- Canonical: https://rewindex.com/company/salesforce/incidents/20004309 · Markdown: https://rewindex.com/company/salesforce/incidents/20004309.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20004309 · Generated 2026-10-18T10:29:27.347Z