ServiceMax incident

Errors when using ServiceMax Application

Notice Resolved View vendor source →

ServiceMax experienced a notice incident on February 11, 2020 affecting Critical Announcements, lasting 3h 28m. The incident has been resolved; the full update timeline is below.

Started
Feb 11, 2020, 04:04 PM UTC
Resolved
Feb 11, 2020, 07:32 PM UTC
Duration
3h 28m
Detected by Pingoru
Feb 11, 2020, 04:04 PM UTC

Affected components

Critical Announcements

Update timeline

  1. investigating Feb 11, 2020, 04:04 PM UTC

    ServiceMax Support has received reports from several customers that intermittent errors are being received when using all aspects of the ServiceMax Application (server and mobile). We have also had reports of similar errors received on non-ServiceMax customizations. The errors displayed vary from Vagabond errors to GAC errors to permission related errors. We are working with both our internal teams and Salesforce on this issue.

  2. investigating Feb 11, 2020, 04:57 PM UTC

    CURRENT STATUS – Salesforce have confirmed that they are experiencing performance degradation on a number of instances. Updates can been seen here - https://status.salesforce.com/incidents/5079 NEXT UPDATE – As more information becomes available from Salesforce updates will be provided.

  3. investigating Feb 11, 2020, 05:39 PM UTC

    Current Status: Salesforce has posted that the issue is resolved. We are following up with impacted customers to confirm resolution. Salesforce Posted Root Cause: The problem was caused by unexpected behavior​ during routine release activity to the​ application tier. The release completed and normal performance was restored. https://status.salesforce.com/incidents/5079

  4. monitoring Feb 11, 2020, 05:45 PM UTC

    Current Status: Salesforce has posted that the issue is resolved. We are following up with impacted customers to confirm resolution. Salesforce Posted Root Cause: The problem was caused by unexpected behavior​ during routine release activity to the​ application tier. The release completed and normal performance was restored. https://status.salesforce.com/incidents/5079

  5. resolved Feb 11, 2020, 07:32 PM UTC

    Current Status: ServiceMax has confirmed resolution. Salesforce Posted Root Cause: The problem was caused by unexpected behavior​ during routine release activity to the​ application tier. The release completed and normal performance was restored. https://status.salesforce.com/incidents/5079