Companies / Salesforce / incidents

Salesforce: Performance Degradation: Core Service

Impact: minorStatus: resolvedStarted Resolved (2.2 h)5 updatesSource: status.salesforce.com (opens in new tab)

Affected components: Core Service1 instance

Timeline of updates

  1. investigating

    We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.

  2. update

    We're aware of an issue impacting Core Services on NA245. Customers are experiencing elevated message queue latency, which may be observed as "out of heap memory" errors. Data pipeline jobs may fail, preventing downstream data retrieval from completing, and asynchronous jobs (e.g., bulk jobs, Apex features) may also be impacted. We are actively investigating the technical trigger, and as a short-term fix are performing service restarts. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  3. update

    During investigations, we established that the level of impact differs from what was initially understood. We have updated the incident posting to reflect the current impact symptoms accurately.

  4. update

    Current remediation efforts indicate positive results as monitoring shows errors ceasing with jobs starting to succeed. We are continuing to perform service restarts in order to mitigate the issue. We'll provide the next update upon completion of service restarts or sooner, if more information becomes available.

  5. update

    After performing service restarts, and monitoring the environment, we’ve confirmed the issue impacting message queue latency, data pipeline jobs, and asynchronous jobs on NA245 has been resolved. Additionally, further investigation into the trigger identified the issue started earlier than initially reported. We have updated the impact start time accordingly. 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.

Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab). Salesforce profile · Recent Salesforce incidents · Markdown · JSON