3708733 - Activity (ServiceAssignment) Remains in LOCKED Status After Attempting to Close

• After closing an Activity (technically, a ServiceAssignment object) in the FSM Mobile app, the object remains in LOCKED status in the cloud
• The ServiceCheckout and attachments are successfully synchronized
• Despite the technician completing the closure on the device, the ServiceAssignment does not transition to Closed
• Logs may show a synchronization conflict, such as OBJECT_BLOCKED (e.g. "Sync V5 – Error type: OBJECT_BLOCKED – Object: ActivityDTO_V43")
• This behavior may occur in some cases if multiple updates or merges are attempted on the same ServiceAssignment
  
  

Note:

The LOCKED status should not be confused with syncStatus=BLOCKED. A ServiceAssignment (Activity) is considered LOCKED once it has been successfully checked out but has not yet been closed. In the scenario described, although the technician clicked the Close button, the Activity remained in the LOCKED state until the system successfully processed the closure and synchronized with the cloud. 

SAP Field Service Management 

activity locked state, sap fsm mobile app, activity closure issue, locked status, synchronization conflict, merge conflict, object blocked error, Sync V5 error, ActivityDTO_V43, clearing merge conflicts, fsm mobile troubleshooting , KBA , CEC-SRV-FSM-WIN , FSM Mobile - Windows , CEC-SRV-FSM-IOS , FSM Mobile - iOS , CEC-SRV-FSM-ADR , FSM Mobile - Android , Problem