Feature Disruption

Initial monitoring is showing positive results. We will continue to observe the environment and will provide an update upon significant changes or if new information becomes available.

We have rolled back the recent change and are monitoring the environment for stability. Affected customers will need to restart their application in order to receive this fix. Users should follow the steps in this article to ensure the application is closed properly: http://sfdc.co/bOfcKD.

We will provide an update in the next 60 minutes or sooner if more information becomes available.

We have identified a recent change to be the potential cause of the issue. Currently, we are working on rolling back that change to alleviate the impact.

We will provide an update in the next 60 minutes or sooner.

We continue to investigate the recent change and are exploring all possible paths and workarounds to mitigate the sync errors occurring in the Field Service Lightning mobile application.

We will provide an update in the next 60 minutes or sooner.

Our investigation is ongoing to validate whether a recent change is the potential cause of the issue. Our monitoring indicates a recent reduction in traffic around 15:15 UTC, which will allow some users to successfully sync records.

We will provide an update in the next 30 minutes or sooner.

We are continuing to investigate the issue affecting customers using the Field Service Lightning mobile application. The issue is believed to only affect Android users. If you are experiencing any sync failures, it is advised not to repeatedly attempt to sync as this will increase the volume of traffic. We are continuing to evaluate whether rolling back to the previous version will resolve the impact.

We will provide an update in the next 30 minutes or sooner.

We are aware of an issue affecting customers while using the Field Service Lightning mobile application. Customers may experience difficulty syncing records and completing operations.
A recent release is the potential trigger of the issue, and we are evaluating if rolling back to the previous version will resolve the impact to customers.

We will provide an update in the next 30 minutes or sooner.